Bug 6498 - Latencytop -d does not work for qemuppc and qemuarm
Summary: Latencytop -d does not work for qemuppc and qemuarm
Status: RESOLVED WONTFIX
Alias: None
Product: General Runtime
Classification: Runtime
Component: General Runtime (show other bugs)
Version: 1.7
Hardware: Other arm
: Low normal
Target Milestone: Future
Assignee: Unassigned
QA Contact: Juan Ramos
URL:
Whiteboard: Roxanna is no longer at Intel
Depends on:
Blocks:
 
Reported: 2014-07-01 14:46 UTC by Catalin Scrieciu
Modified: 2017-06-20 10:49 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: Don't know

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Catalin Scrieciu 2014-07-01 14:46:51 UTC 
While testing Yocto 1.7 M1 RC1 (poky 68824d9b8f6e290da078383316b3f4b732585f2b) we discovered that when executing latencytop -d the following output is diplayed:

root@qemuppc:~# latencytop -d
mount: none is already mounted or /sys/kernel/debug busy
root@qemuppc:~#

This is applicable for both qemuarm and qemuppc.
Comment 1 Saul Wold 2014-07-02 16:05:55 UTC 
sysfs.sh already mounts debugfs, the message is harmess, we could add a check 
to ensure it's not mounted before trying to mount it.
Comment 2 Saul Wold 2014-12-11 16:09:05 UTC 
This is really an upstream bug, I will attempt to file an issue with the upstream maintainer
Comment 3 Richard Purdie 2017-06-20 10:49:19 UTC 
This seems to be an upstream issue in latencytop and is something the upstream software project would have to resolve if they have any interest in doing so, its not something the Yocto Project plan to resolve.