mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Arjan van de Ven" <arjan@linux.intel.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: v2.6.26-rc7: Negative powertop values
Date: Sat, 21 Jun 2008 21:16:37 +0200	[thread overview]
Message-ID: <19f34abd0806211216y4695c532ndb4935082bd8ea1@mail.gmail.com> (raw)

Hi,

I was testing v2.6.26-rc7 by running lmbench and hotplug/-unplugging
CPUs and a few other programs at the same time. Powertop was showing a
negative number of wakeups/second and average C3 residency was
something really insane. Is there anything strange with this schedstat
file, or is there another file I should look at that can explain the
strange powertop numbers? Or maybe it's just an artifact of powertop
and this has nothing to do with the kernel?

    powertop:

    Cn                Avg residency       P-states (frequencies)
    C0 (cpu running)        (105.5%)        1467 Mhz    80.7%
    C1                0.0ms ( 0.0%)         1067 Mhz     0.4%
    C2                0.0ms ( 0.0%)          800 Mhz    19.0%
    C3                0.0ms (1288344194138.5%)

    Wakeups-from-idle per second : -6.2     interval: 2.0s


    # cat /proc/schedstat
    version 14
    timestamp 811305
    cpu0 0 0 0 545 0 5733898 257804 3325833 3064649 6916730262519
21980606970853 5438836
    domain0 <NULL> 1514 1081 425 452096 12 10 0 1081 91 91 0 0 0 0 0
91 5916 4168 1715 1859096 34 13 4 4164 4 0 4 0 0 0 0 0 0 1013 18883 0
    cpu1 0 0 0 1279 0 12508366 1294362 7173738 6484092 1515315020607
22231002791887 11146865
    domain0 <NULL> 313 219 88 154083 10 3 0 219 104 104 0 527 0 0 0
104 1077 894 163 467031 41 5 0 894 1 0 1 0 0 0 0 0 0 455 14689 0


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036

             reply	other threads:[~2008-06-21 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-21 19:16 Vegard Nossum [this message]
2008-06-21 21:16 ` Arjan van de Ven
2008-06-21 21:22   ` Vegard Nossum
2008-07-06 19:48   ` Pavel Machek
2008-07-08 13:52     ` Arjan van de Ven
2008-07-13 11:58       ` Pavel Machek
2008-07-13 15:35         ` Arjan van de Ven
2008-07-14  6:26           ` Pavel Machek
2008-07-13 15:37         ` Arjan van de Ven

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19f34abd0806211216y4695c532ndb4935082bd8ea1@mail.gmail.com \
    --to=vegard.nossum@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=arjan@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®