public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andreas Herrmann <andreas.herrmann3@amd.com>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
	Suresh B Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH 2/5] x86: PAT: fix ambiguous paranoia check in	pat_init()
Date: Wed, 11 Jun 2008 10:35:41 -0700	[thread overview]
Message-ID: <48500CED.4020906@zytor.com> (raw)
In-Reply-To: <20080611094730.GB5889@alberich.amd.com>

Andreas Herrmann wrote:
> 
> For Intel all family 0xf CPUs, and family 6 CPUs starting with model
> 15 are whitelisted.
> 

Arg, sorry, I read the code brokenly.  You're right, of course.

> There seem to be other Intel CPUs that advertise PAT support.
> See cpuinfo output at http://gentoo-wiki.com/Safe_Cflags
> E.g. Pentium M (model 13), Celeron (model 6), Pentium III (model 8).
> (Not sure how correct this information is, though)

Yes, those all have PAT enabled.

> Turn the white- into a blacklist for those remaining CPUs until they
> are verified?

Yes, that would be a suitable course of action; moving it to 
Intel-specific code.  Then the Intel people can worry about lifting the 
remaining blacklisted CPUs.

	-hpa


  parent reply	other threads:[~2008-06-11 17:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 14:05 [PATCH 2/5] x86: PAT: fix ambiguous paranoia check in pat_init() Andreas Herrmann
2008-06-10 22:55 ` Rene Herman
2008-06-10 23:33   ` H. Peter Anvin
2008-06-11  9:47     ` Andreas Herrmann
2008-06-11 15:05       ` [PATCH] x86: enable PAT on (almost) all CPUs that advertise it Andreas Herrmann
2008-06-11 16:44         ` H. Peter Anvin
2008-06-11 17:35       ` H. Peter Anvin [this message]
2008-06-11  9:41   ` [PATCH 2/5] x86: PAT: fix ambiguous paranoia check in pat_init() Andreas Herrmann
2008-06-11 12:58     ` Rene Herman
2008-06-11 16:12       ` Andreas Herrmann
2008-06-12  4:32         ` Rene Herman

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=48500CED.4020906@zytor.com \
    --to=hpa@zytor.com \
    --cc=andreas.herrmann3@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rene.herman@keyaccess.nl \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=venkatesh.pallipadi@intel.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