From: Andi Kleen <andi@firstfloor.org>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Vegard Nossum" <vegard.nossum@gmail.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"S.Çağlar Onur" <caglar@pardus.org.tr>,
Valdis.Kletnieks@vt.edu, "Matt Mackall" <mpm@selenic.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BISECTED] Lots of "rescheduling IPIs" in powertop
Date: Wed, 14 May 2008 13:42:54 +0200 [thread overview]
Message-ID: <87prrp6ri9.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080514090923.GC5607@alberich.amd.com> (Andreas Herrmann's message of "Wed, 14 May 2008 11:09:23 +0200")
Andreas Herrmann <andreas.herrmann3@amd.com> writes:
>
> It depends on the CPU. For AMD CPUs that support MWAIT this is wrong.
> Family 0x10 and 0x11 CPUs will enter C1 on HLT. Powersavings then
^ not
> It might be best to switch off the mwait flag for these AMD CPU
> families like it was introduced with commit
> f039b754714a422959027cb18bb33760eb8153f0 (x86: Don't use MWAIT on AMD
> Family 10)
Then you have to special case everything again. We still need to
work out if the P4 is even correct here or not, but if it's not
i would rather quirk the cpuid reporting on it.
-Andi
next prev parent reply other threads:[~2008-05-14 11:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 20:42 [BISECTED] Lots of "rescheduling IPIs" in powertop Vegard Nossum
2008-05-13 20:54 ` Andi Kleen
2008-05-13 21:09 ` Vegard Nossum
2008-05-13 21:19 ` Andi Kleen
2008-05-14 4:02 ` Arjan van de Ven
2008-05-14 6:58 ` Andi Kleen
2008-05-14 13:55 ` Arjan van de Ven
2008-05-14 15:21 ` Andi Kleen
2008-05-14 6:00 ` Vegard Nossum
2008-05-14 6:56 ` Ingo Molnar
2008-05-14 7:11 ` Vegard Nossum
2008-05-14 9:09 ` Andreas Herrmann
2008-05-14 11:42 ` Andi Kleen [this message]
2008-05-15 16:10 ` Andreas Herrmann
2008-05-16 8:40 ` Ingo Molnar
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=87prrp6ri9.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=andreas.herrmann3@amd.com \
--cc=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@gmail.com \
/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