From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Elena Ufimtseva <ufimtseva@gmail.com>,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, akpm@linux-foundation.org,
tangchen@cn.fujitsu.com, wency@cn.fujitsu.com,
ian.campbell@citrix.com, stefano.stabellini@eu.citrix.com,
mukesh.rathor@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v2 2/2] xen: enable vnuma for PV guest
Date: Tue, 19 Nov 2013 09:46:30 -0500 [thread overview]
Message-ID: <20131119144630.GA5780@phenom.dumpdata.com> (raw)
In-Reply-To: <528B774F.7090902@citrix.com>
On Tue, Nov 19, 2013 at 02:35:59PM +0000, David Vrabel wrote:
> On 19/11/13 14:16, Konrad Rzeszutek Wilk wrote:
> > On Tue, Nov 19, 2013 at 11:54:08AM +0000, David Vrabel wrote:
> >> On 18/11/13 21:58, Elena Ufimtseva wrote:
> >>> Enables numa if vnuma topology hypercall is supported and it is domU.
> >> [...]
> >>> --- a/arch/x86/xen/setup.c
> >>> +++ b/arch/x86/xen/setup.c
> >>> @@ -20,6 +20,7 @@
> >>> #include <asm/numa.h>
> >>> #include <asm/xen/hypervisor.h>
> >>> #include <asm/xen/hypercall.h>
> >>> +#include <asm/xen/vnuma.h>
> >>>
> >>> #include <xen/xen.h>
> >>> #include <xen/page.h>
> >>> @@ -598,6 +599,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_supported())
> >>> + numa_off = 0;
> >>> + else
> >>> + numa_off = 1;
> >>> #endif
> >>> }
> >>
> >> I think this whole #ifdef CONFIG_NUMA can be removed and hence
> >> xen_vnuma_supported() can be removed as well.
> >>
> >> For any PV guest we can call the xen_numa_init() and it will do the
> >> right thing.
> >>
> >> For dom0, the hypercall will either: return something sensible (if in
> >> the future Xen sets something up), or it will error.
> >>
> >> If Xen does not have vnuma support, the hypercall will error.
> >>
> >> In both error cases, the dummy numa node is setup as required.
> >
> > Incorrect. It will end up calling:
> >
> > if (!numa_init(amd_numa_init))
> >
> > which will crash dom0 (see 8d54db795 "xen/boot: Disable NUMA for PV guests.")
> > as that amd_numa_init is called before the dummy node init.
>
> No it won't. Any error path after the check for a PV guest will add the
> dummy node and return success, skipping any of the hardware-specific setup.
Duh! I totally missed 'return' at the end of the check!
However, even with that (so the return), that means
this part won't be called:
649 numa_init(dummy_numa_init);
Which means there won't be any dummy numa setup?
next prev parent reply other threads:[~2013-11-19 14:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 21:58 [PATCH RESEND v2 0/2] xen: vnuma introduction for pv guest Elena Ufimtseva
2013-11-18 21:58 ` [PATCH RESEND v2 1/2] xen: vnuma support for PV guests running as domU Elena Ufimtseva
2013-11-19 11:53 ` David Vrabel
2013-11-18 21:58 ` [PATCH RESEND v2 2/2] xen: enable vnuma for PV guest Elena Ufimtseva
2013-11-19 11:54 ` David Vrabel
2013-11-19 14:16 ` Konrad Rzeszutek Wilk
2013-11-19 14:35 ` David Vrabel
2013-11-19 14:46 ` Konrad Rzeszutek Wilk [this message]
2013-11-19 14:56 ` David Vrabel
2013-11-19 15:19 ` Konrad Rzeszutek Wilk
2013-11-19 15:55 ` David Vrabel
2013-11-19 16:20 ` Konrad Rzeszutek Wilk
2013-11-23 16:48 ` [Xen-devel] " Dario Faggioli
2013-11-19 7:18 ` [Xen-devel] [PATCH RESEND v2 0/2] xen: vnuma introduction for pv guest Dario Faggioli
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=20131119144630.GA5780@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mukesh.rathor@oracle.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tangchen@cn.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=ufimtseva@gmail.com \
--cc=wency@cn.fujitsu.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
Powered by JetHome