public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Venki Pallipadi <venkatesh.pallipadi@intel.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	kernel list <linux-kernel@vger.kernel.org>,
	suresh.b.siddha@intel.com
Subject: Re: [PATCH] x86: pat cpu feature bit setting for known cpus
Date: Tue, 25 Mar 2008 12:08:52 -0700	[thread overview]
Message-ID: <20080325190851.GC30998@linux-os.sc.intel.com> (raw)
In-Reply-To: <86802c440803251103taf4c8f2mb674c3d17f3c2345@mail.gmail.com>

On Tue, Mar 25, 2008 at 11:03:37AM -0700, Yinghai Lu wrote:
> On Tue, Mar 25, 2008 at 6:38 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> > Yinghai Lu wrote:
> >  > [PATCH] x86: pat cpu feature bit setting for known cpus
> >  >
> >  > Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
> >
> >  OK, note previous question: what is the motivation for having this as a
> >  whitelist (as opposed to a blacklist)?
> 
> Venkatesh could tell?

Main reason for white-list at this point is not to be side-tracked by
real or potential erratas on older CPUs. Focussing on getting the support for
this feature on current and future CPUs. If older CPUs have survived all these
days without this feature, they should be doing OK.

Other reason being the amount of testing we get on those older systems. I mean,
any regression on some specific CPU is hard to find unless it is being tested
or someone audits all the errata documents to prepare the blacklist (Unless
we want to have big blacklist which is just !current_whitelist). We do not
have any self test that can detect and report any problematic CPUs that we
can add to the blacklist.

Having said that, if there is a need for this on older CPUs, I am OK with
having this as a blacklist.
 
Thanks,
Venki


  reply	other threads:[~2008-03-25 19:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-25  6:24 [PATCH] x86: pat cpu feature bit setting for known cpus Yinghai Lu
2008-03-25 10:58 ` Ingo Molnar
2008-03-25 13:38 ` H. Peter Anvin
2008-03-25 18:03   ` Yinghai Lu
2008-03-25 19:08     ` Venki Pallipadi [this message]
2008-03-25 20:08       ` Ingo Molnar
2008-03-25 20:38         ` H. Peter Anvin
2008-03-25 23:01           ` H. Peter Anvin
2008-03-25 23:05             ` Yinghai Lu
2008-03-25 23:06               ` H. Peter Anvin
2008-03-25 23:08                 ` Yinghai Lu
2008-03-25 23:38                   ` Pallipadi, Venkatesh
2008-03-26  0:01                     ` Yinghai Lu
2008-03-26  0:10                   ` H. Peter Anvin
2008-03-28 13:41 ` Pavel Machek
2008-03-28 14:51   ` Yinghai Lu
2008-03-30 11:43 ` dean gaudet

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=20080325190851.GC30998@linux-os.sc.intel.com \
    --to=venkatesh.pallipadi@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@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