public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Caron <vcaron@bearstech.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen: disable ACPI NUMA for PV guests
Date: Mon, 13 Dec 2010 23:17:38 +0100	[thread overview]
Message-ID: <1292278658.28988.161.camel@zerohal> (raw)
In-Reply-To: <1291370043-3075-1-git-send-email-ian.campbell@citrix.com>

On Fri, 2010-12-03 at 09:54 +0000, Ian Campbell wrote:
> Xen does not currently expose PV-NUMA information to PV
> guests. Therefore disable NUMA for the time being to prevent the
> kernel picking up on an host-level NUMA information which it might
> come across in the firmware.
> 
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> ---
>  arch/x86/xen/enlighten.c |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> index fbb35cd..7cdf2f3 100644
> --- a/arch/x86/xen/enlighten.c
> +++ b/arch/x86/xen/enlighten.c
> @@ -1195,6 +1195,10 @@ asmlinkage void __init xen_start_kernel(void)
>  
>  	xen_smp_init();
>  
> +#ifdef CONFIG_ACPI_NUMA
> +	acpi_numa = -1;
> +#endif
> +
>  	pgd = (pgd_t *)xen_start_info->pt_base;
>  
>  	__supported_pte_mask |= _PAGE_IOMAP;

  This made it thru 2.6.32-29 in Debian on 10 dec and works like a
charm, Dell R410 properly booting with hypervisor Xen 4.0.1.

  Thanks a lot for your help and responsiveness.



      reply	other threads:[~2010-12-13 22:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1291369764.5514.15168.camel@zakaz.uk.xensource.com>
2010-12-03  9:54 ` [PATCH] xen: disable ACPI NUMA for PV guests Ian Campbell
2010-12-13 22:17   ` Vincent Caron [this message]

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=1292278658.28988.161.camel@zerohal \
    --to=vcaron@bearstech.com \
    --cc=ian.campbell@citrix.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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