mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: aherrman@arcor.de
To: "H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, andreas.herrmann3@amd.com
Subject: RE: [PATCH] x86: limit mwait_idle to Intel CPUs
Date: Thu, 5 Apr 2007 23:12:08 +0200	[thread overview]
Message-ID: <20070405211208.GA8126@tweety.malo> (raw)
In-Reply-To: <46152A04.1010009@zytor.com>

Peter Anvin wrote:
> Andreas Herrmann wrote:
> > 
> > It is not equivalent. Usually users check /proc/cpuinfo for their
> > CPU features. Deleting that flag is kind of obfuscation.
> > 
> > I guess some time ago people did not care about their "svm" or "vmx"
> > flags. Nowadays (e.g. with kvm) some people are quite happy
> > if one of those strings occurs in /proc/cpuinfo (and they are quite
> > disappointed if this feature was disabled by BIOS).
> > 

> What you're saying is that you want it to appear in /proc/cpuinfo for 
> marketing reasons even though it's not usable.

Bruellller!
So you are saying I am a marketing guy -- wasn't aware of that.
Just big fun.

> 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.

> 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.


Regards,

Andreas


  parent reply	other threads:[~2007-04-05 21:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 14:00 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 [this message]
2007-04-05 21:19             ` H. Peter Anvin
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=20070405211208.GA8126@tweety.malo \
    --to=aherrman@arcor.de \
    --cc=ak@suse.de \
    --cc=andreas.herrmann3@amd.com \
    --cc=hpa@zytor.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

all inboxes | Powered by JetHome®