WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 1394] New: cpu idle time / cpufreq residency become extr

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1394] New: cpu idle time / cpufreq residency become extremely large
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sat, 6 Dec 2008 03:37:18 -0800
Delivery-date: Sat, 06 Dec 2008 03:37:23 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1394

           Summary: cpu idle time / cpufreq residency become extremely large
           Product: Xen
           Version: unstable
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: haicheng.li@xxxxxxxxx


Environment:
------------
Service Arch (ia32/ia32e/IA64): 
Guest Arch (ia32/ia32e/IA64): 
Guest OS Type (Linux/Windows):
Change Set: 
Hardware: 
Other:


Bug detailed description:
--------------------------
idle time / cpufreq residency output by xenpm could be very large.


Reproduce steps:
----------------
NOTICE that it may not be reproduced successfully every time.
1. boot with cpuidle cpufreq=xen hpetbroadcast
2. run `xenpm` command
3. check the idle time / cpufreq data

Current result:
----------------
[root@nhm-ep ~]# xenpm -c
cpu id               : 0
total C-states       : 3
idle time(ms)        : 125228
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000008117]
                       residency  [00000000000000005031 ms]
C2                   : transition [00000000000000031715]
                       residency  [00000000000000102309 ms]

cpu id               : 1
total C-states       : 3
idle time(ms)        : 18446744067564                   <-------------
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000001010]
                       residency  [00000000000000000531 ms]
C2                   : transition [00000000000000015758]
                       residency  [00000000000000108875 ms]

cpu id               : 2
total C-states       : 3
idle time(ms)        : 18446744066087
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000002089]
                       residency  [00000000000000000899 ms]
C2                   : transition [00000000000000017678]
                       residency  [00000000000000106361 ms]

cpu id               : 3
total C-states       : 3
idle time(ms)        : 18446744067795
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000003739]
                       residency  [00000000000000000639 ms]
C2                   : transition [00000000000000016164]
                       residency  [00000000000000108350 ms]

cpu id               : 4
total C-states       : 3
idle time(ms)        : 18446744064338
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000002996]
                       residency  [00000000000000001255 ms]
C2                   : transition [00000000000000022124]
                       residency  [00000000000000105717 ms]

cpu id               : 5
total C-states       : 3
idle time(ms)        : 18446744067420
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000001263]
                       residency  [00000000000000000725 ms]
C2                   : transition [00000000000000016881]
                       residency  [00000000000000107979 ms]

cpu id               : 6
total C-states       : 3
idle time(ms)        : 18446744064879
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000001915]
                       residency  [00000000000000001088 ms]
C2                   : transition [00000000000000019183]
                       residency  [00000000000000104932 ms]

cpu id               : 7
total C-states       : 3
idle time(ms)        : 18446744067147
C0                   : transition [00000000000000000000]
                       residency  [00000000000000000000 ms]
C1                   : transition [00000000000000006790]
                       residency  [00000000000000007864 ms]
C2                   : transition [00000000000000049513]
                       residency  [00000000000000097401 ms]


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>