<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>164</bug_id>
          
          <creation_ts>2010-07-29 17:39:45 +0000</creation_ts>
          <short_desc>latencytop NOT functional due to the kernel configuration</short_desc>
          <delta_ts>2010-12-21 06:07:24 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>Meta-yocto</product>
          <component>meta-yocto</component>
          <version>0.9</version>
          <rep_platform>x86</rep_platform>
          <op_sys>x86</op_sys>
          <bug_status>VERIFIED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>0.9 M3</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Lianhao Lu">lianhao.lu</reporter>
          <assigned_to name="Bruce Ashfield">bruce.ashfield</assigned_to>
          <cc>dexuan.cui</cc>
    
    <cc>jessica.zhang</cc>
    
    <cc>kevin.tian</cc>
    
    <cc>liping.ke</cc>
    
    <cc>poky.bs.watcher</cc>
    
    <cc>poky.watcher</cc>
    
    <cc>richard.purdie</cc>
    
    <cc>sgw</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          <cf_verified>Program Management</cf_verified>
          <cf_docchange>---</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>9160</commentid>
    <comment_count>0</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2010-07-29 17:39:45 +0000</bug_when>
    <thetext>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...</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9164</commentid>
    <comment_count>1</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-07-29 18:24:54 +0000</bug_when>
    <thetext>(In reply to comment #0)
&gt; I tried with the kernel of
&gt; bzImage-2.6.34+git0+09a39c638dd65dc27c549c119abe1af2631b2ae0-r2-qemux86-20100728070622.bin
&gt;  and the rootfs of poky-image-sdk-qemux86-20100728070622.rootfs.ext3 from the
&gt; auto
&gt; builder, but the latencytop is  NOT functional with the following error message
&gt; got printed on the screen:
&gt; Please enable the CONFIG_LATENCYTOP configuration in your kernel.
&gt; Exiting...

I did add CONFIG_LATENCYTOP=y for qemux86.
Please see commit 6b2eec3657afc348a48ac31cd2e0413929afa3d6.
I&apos;ll try to reproduce this bug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9165</commentid>
    <comment_count>2</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2010-07-29 18:29:18 +0000</bug_when>
    <thetext>Looks like commit 6b2eec3657afc348a48ac31cd2e0413929afa3d6 only added configuration for netbook, no qemu or emenlow.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9168</commentid>
    <comment_count>3</comment_count>
    <who name="Kevin Tian">kevin.tian</who>
    <bug_when>2010-07-29 18:40:06 +0000</bug_when>
    <thetext>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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9169</commentid>
    <comment_count>4</comment_count>
    <who name="Dexuan Cui">dexuan.cui</who>
    <bug_when>2010-07-29 18:50:32 +0000</bug_when>
    <thetext>(In reply to comment #3)
&gt; Qemu targets are using WR kernel, while so far its configs are not exposed to
&gt; poky. We have to ask WR for adding related options

Hi Saul, as Kevin explained, we can&apos;t change WR kernel&apos;s config, so I think we may as well assign the bug to WR -- Bruce? Can you please do the reassignment?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9232</commentid>
    <comment_count>5</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2010-08-04 07:24:11 +0000</bug_when>
    <thetext>I&apos;ll take care of updating this, but it is pending on some
other updates to the kernel. ETA is in a few days.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9258</commentid>
    <comment_count>6</comment_count>
    <who name="Bruce Ashfield">bruce.ashfield</who>
    <bug_when>2010-08-05 15:07:40 +0000</bug_when>
    <thetext>I pushed a set of default latency top options to the windriver kernel
repo. 

Until we get the multi-srcrev code working, you&apos;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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>9759</commentid>
    <comment_count>7</comment_count>
    <who name="Lianhao Lu">lianhao.lu</who>
    <bug_when>2010-09-13 02:38:25 +0000</bug_when>
    <thetext>Verified. The WR kernel now is configured with default setting CONFIG_LATENCYTOP=y for qemux86.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>