xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xensource.com
Subject: [GIT PULL] (xen) stable/for-linus-3.7-rc7-tag
Date: Mon, 24 Sep 2012 09:43:43 -0400	[thread overview]
Message-ID: <20120924134343.GA31618@phenom.dumpdata.com> (raw)

Hey Linus,

I've one fix for which I got the Tested-by right after I sent you a git pull on
Friday. If you have some extra patches for rc7, please consider pulling it.
If you don't have any - I will just stick this in my for-v3.7.

git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.6-rc7-tag

It is a bug-fix when we run the initial PV guest on a AMD K8 machine
and have CONFIG_AMD_NUMA enabled and detect the NUMA topology from the Northbridge.

We end up in the situation where the initial domain gets too much information
and gets confused and crashes - the fix is to restrict the domain to get the
information - and we do it by just disabling NUMA on the PV guest (the hypervisor is
still able to do its proper NUMA allocations of guests). It is OK to disable the PV
guest from accessing NUMA data as right now we do not inject any NUMA node information
to the PV guests. When we do get to that point, then this patch will have to be reverted.

Konrad Rzeszutek Wilk (1):
      xen/boot: Disable NUMA for PV guests.

 arch/x86/xen/setup.c |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

                 reply	other threads:[~2012-09-24 13:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20120924134343.GA31618@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).