Bug 164 - latencytop NOT functional due to the kernel configuration
Summary: latencytop NOT functional due to the kernel configuration
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 0.9
Hardware: x86 x86
: Medium major
Target Milestone: 0.9 M3
Assignee: Bruce Ashfield
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2010-07-29 17:39 UTC by Lianhao Lu
Modified: 2010-12-21 06:07 UTC (History)
8 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified: Program Management
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lianhao Lu 2010-07-29 17:39:45 UTC
I tried with the kernel of
bzImage-2.6.34+git0+09a39c638dd65dc27c549c119abe1af2631b2ae0-r2-qemux86-20100728070622.bin
 and the rootfs of poky-image-sdk-qemux86-20100728070622.rootfs.ext3 from the auto
builder, but the latencytop is  NOT functional with the following error message got printed on the screen:

Please enable the CONFIG_LATENCYTOP configuration in your kernel.
Exiting...
Comment 1 Dexuan Cui 2010-07-29 18:24:54 UTC
(In reply to comment #0)
> I tried with the kernel of
> bzImage-2.6.34+git0+09a39c638dd65dc27c549c119abe1af2631b2ae0-r2-qemux86-20100728070622.bin
>  and the rootfs of poky-image-sdk-qemux86-20100728070622.rootfs.ext3 from the
> auto
> builder, but the latencytop is  NOT functional with the following error message
> got printed on the screen:
> Please enable the CONFIG_LATENCYTOP configuration in your kernel.
> Exiting...

I did add CONFIG_LATENCYTOP=y for qemux86.
Please see commit 6b2eec3657afc348a48ac31cd2e0413929afa3d6.
I'll try to reproduce this bug.
Comment 2 Lianhao Lu 2010-07-29 18:29:18 UTC
Looks like commit 6b2eec3657afc348a48ac31cd2e0413929afa3d6 only added configuration for netbook, no qemu or emenlow.
Comment 3 Kevin Tian 2010-07-29 18:40:06 UTC
Qemu targets are using WR kernel, while so far its configs are not exposed to poky. We have to ask WR for adding related options
Comment 4 Dexuan Cui 2010-07-29 18:50:32 UTC
(In reply to comment #3)
> Qemu targets are using WR kernel, while so far its configs are not exposed to
> poky. We have to ask WR for adding related options

Hi Saul, as Kevin explained, we can't change WR kernel's config, so I think we may as well assign the bug to WR -- Bruce? Can you please do the reassignment?
Comment 5 Bruce Ashfield 2010-08-04 07:24:11 UTC
I'll take care of updating this, but it is pending on some
other updates to the kernel. ETA is in a few days.
Comment 6 Bruce Ashfield 2010-08-05 15:07:40 UTC
I pushed a set of default latency top options to the windriver kernel
repo. 

Until we get the multi-srcrev code working, you'll need to explicitly
remove your clone of the windriver Linux kernel in sources and
sources/git to see the changes.

These have been configure and compile, but not runtime tested at
this point.  Return the bug, if there are still issues with this.
Comment 7 Lianhao Lu 2010-09-13 02:38:25 UTC
Verified. The WR kernel now is configured with default setting CONFIG_LATENCYTOP=y for qemux86.