From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>,
Yinghai Lu <yhlu.kernel@gmail.com>,
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 16:01:14 -0700 [thread overview]
Message-ID: <47E9843A.1060702@zytor.com> (raw)
In-Reply-To: <47E962AE.9040307@zytor.com>
H. Peter Anvin wrote:
> Ingo Molnar wrote:
>> * Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:
>>
>>>>> 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.
>>
>> well, the upside would be that since most testing of Linux kernels is
>> done on _old_ hardware (people tend to risk their old hw first ;-),
>> we'd get faster convergence of the codebase, even though we have the
>> risk of erratas (known and unknown ones alike). Code that artificially
>> limits its utility is almost always slow to stabilize.
>>
>
> Yes, using a whitelist of this type is wrong, IMO, and smells faintly of
> vendor-lockin.
>
By the way, I want to clarify: I didn't mean it was *intended* as
vendor-lockin, just that it's an undesirable effect of this.
-hpa
next prev parent reply other threads:[~2008-03-25 23:02 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
2008-03-25 20:08 ` Ingo Molnar
2008-03-25 20:38 ` H. Peter Anvin
2008-03-25 23:01 ` H. Peter Anvin [this message]
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=47E9843A.1060702@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
--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