From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Elena Ufimtseva <ufimtseva@gmail.com>,
lccycc123@gmail.com, george.dunlap@eu.citrix.com,
xen-devel@lists.xen.org, david.vrabel@citrix.com, msw@amazon.com,
boris.ostrovsky@oracle.com
Subject: Re: [PATCH RFC v2 2/2] linux/vnuma: Enables NUMA for domu PV guest
Date: Fri, 27 Sep 2013 13:03:58 -0400 [thread overview]
Message-ID: <20130927170358.GA11397@phenom.dumpdata.com> (raw)
In-Reply-To: <1379517289.18543.154.camel@Abyss>
On Wed, Sep 18, 2013 at 05:14:49PM +0200, Dario Faggioli wrote:
> On mar, 2013-09-17 at 04:34 -0400, Elena Ufimtseva wrote:
> > diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
> > index 8f3eea6..2f2d28e 100644
> > --- a/arch/x86/xen/setup.c
> > +++ b/arch/x86/xen/setup.c
> >
> > #include <xen/xen.h>
> > #include <xen/page.h>
> > @@ -583,6 +584,9 @@ void __init xen_arch_setup(void)
> > WARN_ON(xen_set_default_idle());
> > fiddle_vdso();
> > #ifdef CONFIG_NUMA
> > - numa_off = 1;
> > + if (!xen_initial_domain() && xen_vnuma_support())
> > + numa_off = 0;
> > + else
> > + numa_off = 1;
> > #endif
> > }
> I can't be positive about this, but I think that, if we go for David's
> suggestions of:
> - testing for the hypercall being actually supported,
> - calling dummy_numa_init() directly from within xen_numa_init (in
> case something go wrong), instead of going through all the
> alternatives from x86_numa_init()
>
> then we can even get rid of this numa_off=0|1 all together (which is
> also something David was already suggesting, AFAICR).
You could do:
if (xen_initial_domain()) && !xen_vnuma_support())
numa_off = 1;
And just do that. The PV guest (the plain one) can then go on
and just do the dummy one.
>
> It would be nice to know what the issue was at the time they had to
> introduce this, and whether we can get to do some testing on any of the
> boxes where it was exploding.
konrad@phenom:~/linux$ git annotate arch/x86/xen/setup.c|grep numa_off
8d54db795 (Konrad Rzeszutek Wilk 2012-08-17 10:22:37 -0400 601) numa_off = 1;
konrad@phenom:~/linux$ git show 8d54db795
commit 8d54db795dfb1049d45dc34f0dddbc5347ec5642
Author: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date: Fri Aug 17 10:22:37 2012 -0400
xen/boot: Disable NUMA for PV guests.
....
this scanning is still enabled (K8 and Fam10h, not Bulldozer class)
..
Pid: 0, comm: swapper Not tainted 3.3.6 #1 AMD Dinar/Dinar
>
> I'll investigate more, in the meanwhile, does anyone had any clue?
>
> Dario
>
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-09-27 17:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 8:33 [PATCH RFC v2 0/2] linux/vnuma: vNUMA PV guest support introduction Elena Ufimtseva
2013-09-17 8:34 ` [PATCH RFC v2 1/2] linux/vnuma: vNUMA for PV domu guest Elena Ufimtseva
2013-09-17 14:10 ` David Vrabel
2013-09-18 6:16 ` Elena Ufimtseva
2013-09-18 7:17 ` Dario Faggioli
2013-09-18 7:41 ` Elena Ufimtseva
2013-09-18 12:23 ` David Vrabel
2013-09-17 14:21 ` Boris Ostrovsky
2013-09-18 6:30 ` Elena Ufimtseva
2013-09-18 7:33 ` Dario Faggioli
2013-09-18 7:39 ` Elena Ufimtseva
2013-09-18 16:04 ` Dario Faggioli
2013-09-17 8:34 ` [PATCH RFC v2 2/2] linux/vnuma: Enables NUMA for domu PV guest Elena Ufimtseva
2013-09-17 14:17 ` David Vrabel
2013-09-17 14:37 ` Dario Faggioli
2013-09-18 6:32 ` Elena Ufimtseva
2013-09-18 15:14 ` Dario Faggioli
2013-09-27 17:03 ` Konrad Rzeszutek Wilk [this message]
2013-09-18 16:16 ` [PATCH RFC v2 0/2] linux/vnuma: vNUMA PV guest support introduction Dario Faggioli
2013-09-18 16:20 ` Elena Ufimtseva
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=20130927170358.GA11397@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=lccycc123@gmail.com \
--cc=msw@amazon.com \
--cc=ufimtseva@gmail.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).