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:32:30 -0700	[thread overview]
Message-ID: <4CADE80E.8050905@zytor.com> (raw)
In-Reply-To: <4CAE0373020000780001B50E@vpn.id2.novell.com>

On 10/07/2010 08:29 AM, Jan Beulich wrote:
>>
>> 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.
> 
> The only possible (afaict) way to address this would be to check for
> the erratum in the boot code, and establish 4k page mappings from
> the beginning. That's likely going to be ugly though.
> 

Well, I guess we could do on 64 bits what we do on 32 bits, and always
use 4K pages for the initial bootstrap, to then be coalesced if PSE is
supported.  Again, ugly.

> The main reason I was asking was not so much to trigger a code
> change, but to understand the implications (since both the comment
> in the code and the changeset comment don't really hint at this
> leaving a problem open for 64-bit), to some degree to understand
> whether e.g. Xen would also need such a workaround (if anyone
> cares to run Xen on Atoms).

Well, keep in mind that the right thing really is to get the microcode
update into the CPU early... i.e. in the BIOS, or in a pinch, from the
bootloader -- but before the kernel runs.

	-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:32 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
2010-10-07 15:29           ` Jan Beulich
2010-10-07 15:32             ` H. Peter Anvin [this message]
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=4CADE80E.8050905@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