public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patch disabling use of PSE on Atom CPUs with a certain	 erratum
Date: Thu, 07 Oct 2010 08:10:43 -0700	[thread overview]
Message-ID: <4CADE2F3.8000908@zytor.com> (raw)
In-Reply-To: <4CADFAE6020000780001B4DC@vpn.id2.novell.com>

On 10/07/2010 07:52 AM, Jan Beulich wrote:
>>>> On 07.10.10 at 16:08, "H. Peter Anvin" <hpa@zytor.com> wrote:
>> On 10/07/2010 07:01 AM, Jan Beulich wrote:
>>>>
>>>> Those Atoms don't have 64-bit support.
>>>
>>> That's different from what I found looking around on the web.
>>>
>>
>> Do tell...
> 
> E.g.
> 
> http://en.wikipedia.org/wiki/List_of_Intel_Atom_microprocessors
> 
> in particular the Atom 230 and Atom 330 (which to my reading match
> the spec updates for the 200 and 300 series, which in turn exhibit
> the erratum in question).
> 

You're right... I misremembered.  The question is what to do at this
point, since we're already in trouble.  A possible failure on startup
seems better than a state in which we could get data corruption at
almost any time.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-10-07 15:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-07  9:12 patch disabling use of PSE on Atom CPUs with a certain erratum Jan Beulich
2010-10-07 13:46 ` H. Peter Anvin
2010-10-07 14:01   ` Jan Beulich
2010-10-07 14:08     ` H. Peter Anvin
2010-10-07 14:52       ` Jan Beulich
2010-10-07 15:10         ` H. Peter Anvin [this message]
2010-10-07 15:29           ` Jan Beulich
2010-10-07 15:32             ` H. Peter Anvin
2010-10-18 23:23               ` Yuhong Bao

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=4CADE2F3.8000908@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@novell.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