From: Dario Faggioli <dario.faggioli@citrix.com>
To: Matt Wilson <msw@amazon.com>
Cc: "konrad.r.wilk" <konrad.r.wilk@gmail.com>,
David Vrabel <david.vrabel@citrix.com>,
Elena Ufimtseva <ufimtseva@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 1/2] linux/vnuma: vnuma support for pv guest
Date: Wed, 28 Aug 2013 15:08:31 +0200 [thread overview]
Message-ID: <1377695311.5255.34.camel@Abyss> (raw)
In-Reply-To: <20130828013733.GB2840@u109add4315675089e695.ant.amazon.com>
[-- Attachment #1.1: Type: text/plain, Size: 1726 bytes --]
On mar, 2013-08-27 at 18:37 -0700, Matt Wilson wrote:
> On Tue, Aug 27, 2013 at 06:27:15PM -0700, Matt Wilson wrote:
> > On Tue, Aug 27, 2013 at 04:52:59AM -0400, Elena Ufimtseva wrote:
> > > Uses subop hypercall to request XEN about vnuma topology.
> > > Sets the memory blocks (aligned by XEN), cpus, distance table
> > > on boot. NUMA support should be compiled in kernel.
> >
> > Are we *really sure* that we want to go this route for PV vNUMA?
> > Couldn't we build just enough(tm) of the ACPI tables to express the
> > NUMA topology when constructing the domain? That's what we do for the
> > e820 map.
>
> Ignore me somewhat, since the e820 information is retrieved via
> hypercall similar to what you're proposing.
>
:-)
> Still, if there's some way that we can reuse existing Linux code
> rather than bolting on a completely parallel mechanism to set this up
> under PV I think it'd be better.
>
Well, it looks to me that Elena is reusing quite a bit of it, isn't she?
All she's providing is a new initialization function ( xen_numa_init()
), as it is happening already for ACPI NUMA, NUMAQ, and other NUMA
implementations.
In practice, while ACPI based NUMA code parses the ACPI tables in
acpi_numa_init(), PV vNUMA parses the information coming from an
hypercall xen_numa_init(). From that point on, Linux that steps-in and
do everything else "as usual".
Isn't that enough sharing?
Thanks and Regards,
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)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-28 13:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:52 [PATCH RFC 0/2] linux/vnuma: vnuma topology PV guest Elena Ufimtseva
2013-08-27 8:52 ` [PATCH RFC 1/2] linux/vnuma: vnuma support for pv guest Elena Ufimtseva
2013-08-27 13:52 ` David Vrabel
2013-08-27 14:33 ` Konrad Rzeszutek Wilk
2013-08-28 13:41 ` Elena Ufimtseva
2013-08-28 23:12 ` Dario Faggioli
2013-08-29 14:07 ` Konrad Rzeszutek Wilk
2013-08-28 1:27 ` Matt Wilson
2013-08-28 1:37 ` Matt Wilson
2013-08-28 13:08 ` Dario Faggioli [this message]
2013-08-28 13:39 ` George Dunlap
2013-08-28 16:01 ` Konrad Rzeszutek Wilk
2013-08-28 16:38 ` Matt Wilson
2013-08-28 20:10 ` Elena Ufimtseva
2013-08-28 23:25 ` Matt Wilson
2013-08-29 9:16 ` George Dunlap
2013-08-28 22:21 ` Dario Faggioli
2013-08-29 0:11 ` Matt Wilson
2013-08-29 13:41 ` David Vrabel
2013-08-29 14:23 ` Konrad Rzeszutek Wilk
2013-08-29 14:32 ` George Dunlap
2013-08-29 14:51 ` Konrad Rzeszutek Wilk
2013-08-29 22:29 ` Dario Faggioli
2013-08-30 12:57 ` Konrad Rzeszutek Wilk
2013-08-27 8:53 ` [PATCH RFC 2/2] linux/vnuma: Enables NUMA support for PV guest Elena Ufimtseva
2013-08-27 13:35 ` David Vrabel
2013-08-27 15:36 ` Konrad Rzeszutek Wilk
2013-08-27 14:17 ` Konrad Rzeszutek Wilk
2013-08-27 13:48 ` [PATCH RFC 0/2] linux/vnuma: vnuma topology " David Vrabel
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=1377695311.5255.34.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.r.wilk@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 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.