| Summary: | Tracing: tuna, oscilloscope recipes | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Song Liu <song.liu> |
| Component: | meta-yocto | Assignee: | Unassigned <unassigned> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | bluelightning, dvhart, jessica.zhang, poky.bs.watcher, poky.watcher, sgw, tom.zanussi |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | (Scheduled) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Song Liu
2011-10-04 22:22:38 UTC
These graphical tools are most useful apparently for RT systems. Tuna is a top-like utility that allows you to change process settings such as scheduling priority and policy. Oscilloscope continuously displays the output of 'cyclictest -v' in a scope-like display, essentially showing the scheduling latencies for real-time processes. Both applications are implemented in Python. Oscilloscope uses the stdout of cyclictest – apparently if you set it to generate too little, you get inaccurate results, too high and it can't keep up. Also doesn't seem to support network natively, would probably have to use netcat or modify it Essentially we need to decide whether it makes sense to add this. It was initially suggested by Bruce, Darren may be the best person to provide input since it deals with RT. Tom, should we move to 1.4? Yes, that makes sense to me. Assigning to dvhart for RT So we haven't got to this by now and it's rather unlikely that we will, so I'm marking it as WONTFIX. (That's not to say that we can't add recipes for these in future should they be needed.) |