| Summary: | 'perf scripts' integration | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Song Liu <song.liu> |
| Component: | meta-yocto | Assignee: | Jessica <jessica.zhang> |
| Status: | RESOLVED OBSOLETE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | dvhart, jessica.zhang, lianhao.lu, poky.bs.watcher, poky.watcher, tom.zanussi |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Song Liu
2011-10-04 13:38:49 UTC
This is very similar to the SystemTap case (Bug 1551), except in this case we don't have a lot of user setup to do, essentially we just run 'perf script' on the remote system and get the output piped back. Like SystemTap, we would really like to be able to run perf scripts as seamlessly as possible from Eclipse too. Functionality-wise, the user should be able to simply create a perf script in a window and run it. We also need to be able to specify script params. The output should be available just like the output from the other supported tracing and debugging tools. Implementation-wise, we could just remotely execute perf underneath, but if it's better to create an oprofileui-type mechanism to tie into Eclipse protocols as much as possible, even better. We should be able to leverage what we do in Eclipse for the SystemTap case and apply it to the perf script case as they're similar. Of course, since we're in an IDE it would be nice if the IDE could understand SystemTap and provide Systemtap-specific completion and syntax highlighting, but that's not what this task is about. change to post 1.2 since the work on Tom's end is pushed out Hard to schedule time to work on this, but definitly won't happen in M3 timeframe The requirement for this feature is extremly low atm, close now, may open later if there's strong demand |