[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080513210217.59a7ca65@infradead.org>
Date: Tue, 13 May 2008 21:02:17 -0700
From: Arjan van de Ven <arjan@...radead.org>
To: Andi Kleen <andi@...stfloor.org>
Cc: Vegard Nossum <vegard.nossum@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Andreas Herrmann <andreas.herrmann3@....com>,
"S.Çağlar Onur" <caglar@...dus.org.tr>,
Valdis.Kletnieks@...edu, Matt Mackall <mpm@...enic.com>,
linux-kernel@...r.kernel.org
Subject: Re: [BISECTED] Lots of "rescheduling IPIs" in powertop
On Tue, 13 May 2008 23:19:47 +0200
Andi Kleen <andi@...stfloor.org> wrote:
>
> Ok the CPU reports it doesn't support any C states in MWAIT. If that
> is correct then it would be correct to not use MWAIT idle and might
> actually save more power to not use it.
what does the current SVN powertop say on this cpu?
>
> I don't know if that's true or not. Do you have a power meter perhaps?
> If yes can you measure if there's a difference between mwait=idle /
> default on your box when it is idle?
>
> [cc Arjan he might now if that CPU is supposed to support C1 in MWAIT]
I wasn't aware that P4's supported mwait in this way; I thought it was
core and later.
> CPU reports it supports C1/C2/C3. Are you sure there is a difference
> on that box? The code should have kept using MWAIT because it checks
> C1. Please double check.
The check is .. dubious I suspect... because the cpuid bits are not
actually the prime source of information, the BIOS is.
If the bios says mwait is usable, we need to use it with the values IT
gives us.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists