From: "H. Peter Anvin" <hpa@zytor.com>
To: aherrman@arcor.de
Cc: Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org, andreas.herrmann3@amd.com
Subject: Re: [PATCH] x86: limit mwait_idle to Intel CPUs
Date: Thu, 05 Apr 2007 14:19:33 -0700 [thread overview]
Message-ID: <461567E5.7080905@zytor.com> (raw)
In-Reply-To: <20070405211208.GA8126@tweety.malo>
aherrman@arcor.de wrote:
>
>> The ones in /proc/cpuinfo are cooked values anyway; there is plenty of
>> history to that effect.
>
> I don't know this history. And I don't care.
> I thought /proc/cpuinfo should show an (almost) complete list
> of CPU features. If this is not the case it's a pity.
>
It's a list of features which are implemented and working, as far as
they make sense. In other words, it's *Linux* concept of the feature
set of the CPU.
>> I would agree with Andi that if as far as Linux is concerned mwait is
>> unusable on AMD Fam10 processors, then the CPU detection code should
>> turn this bit off on AMD Fam10 processors.
>
> And finally I was not aware that you and Andi think of monitor/mwait
> as a synonym for Intel's native C-States.
>
> So I guess, what you really want is that for AMD CPUs the
> monitor-flag (aka native C-state-flag) gets removed.
>
> And if somedays another use case for monitor/mwait appears, the flag
> has to be reintroduced for AMD CPUs.
>
> Fine with me.
> The only drawback is that Andi's idea of idle=mwait wouldn't make
> sense anymore.
Well, if there is use for the AMD implementation of monitor/mwait, then
that's a different situation, and probably would call for multiple
feature bits.
-hpa
next prev parent reply other threads:[~2007-04-05 21:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 14:00 [PATCH] x86: limit mwait_idle to Intel CPUs Andreas Herrmann
2007-04-05 14:24 ` Andi Kleen
2007-04-05 14:44 ` Andreas Herrmann
2007-04-05 15:37 ` Andi Kleen
2007-04-05 16:20 ` Andreas Herrmann
2007-04-05 16:55 ` H. Peter Anvin
2007-04-05 17:06 ` Markus Rechberger
2007-04-05 17:36 ` H. Peter Anvin
2007-04-05 21:12 ` aherrman
2007-04-05 21:19 ` H. Peter Anvin [this message]
2007-04-05 17:05 ` Andi Kleen
2007-04-05 14:46 ` Langsdorf, Mark
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=461567E5.7080905@zytor.com \
--to=hpa@zytor.com \
--cc=aherrman@arcor.de \
--cc=ak@suse.de \
--cc=andreas.herrmann3@amd.com \
--cc=linux-kernel@vger.kernel.org \
/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