All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: konrad@darnok.org, linux-kernel@vger.kernel.org, x86@kernel.org,
	mingo@redhat.com, tglx@linutronix.de, stable@kernel.org
Subject: Re: [PATCH] x86/i386: Check PSE bit before using PAGE_KERNEL_LARGE.
Date: Thu, 31 May 2012 16:35:44 -0400	[thread overview]
Message-ID: <20120531203544.GA19420@phenom.dumpdata.com> (raw)
In-Reply-To: <4FC7D2AE.9080603@zytor.com>

On Thu, May 31, 2012 at 01:21:02PM -0700, H. Peter Anvin wrote:
> On 05/31/2012 12:40 PM, Konrad Rzeszutek Wilk wrote:
> > During bootup we would unconditionally do this on any
> > machine that was built with CONFIG_NUMA=y on i386:
> > 
> > setup_arch
> >   \-initmem_init
> >       \-x86_numa_init (with dummy_init as callback)
> >           \- init_alloc_remap
> >                \- set_pmd_pfn (with PAGE_PSE)
> > 
> > without checking to see if the CPU supports PSE. This
> > patch adds that and also allows the init_alloc_remap function
> > to properly work by falling back on PTEs.
> > 
> 
> Well, the code looks like it is PAE-specific, and PAE implies PSE.

I have to double check - but I think a kernel built with CONFIG_HIGHMEM64=y
and CONFIG_NUMA=y would boot on a Pentium II which can't do PAE.

But perhaps there are some other checks that would halt the kernel
before it even got there?

> 
> Xen breaks that, but that is a divergence of Xen from x86.

It certainly does <sigh>. And that is how I spotted this - b/c the
PMD would fail (with tons of mutlicalls warnings) - and the PTE's
would still point to the old PFNs.

  reply	other threads:[~2012-05-31 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 19:40 [PATCH] x86/i386: Check PSE bit before using PAGE_KERNEL_LARGE Konrad Rzeszutek Wilk
2012-05-31 20:21 ` H. Peter Anvin
2012-05-31 20:35   ` Konrad Rzeszutek Wilk [this message]
2012-05-31 23:02     ` H. Peter Anvin

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=20120531203544.GA19420@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=hpa@zytor.com \
    --cc=konrad@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.