From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>,
Elena Ufimtseva <ufimtseva@gmail.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH for-4.5] xen: vnuma: expose vnode_to_pnode to guest
Date: Mon, 10 Nov 2014 12:42:07 +0100 [thread overview]
Message-ID: <1415619727.3717.28.camel@Abyss> (raw)
In-Reply-To: <20141110110936.GA28360@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 2195 bytes --]
On Mon, 2014-11-10 at 11:09 +0000, Wei Liu wrote:
> On Mon, Nov 10, 2014 at 11:51:28AM +0100, Dario Faggioli wrote:
>
> > I'm 100% ok to re-start that discussion here and now... however, how
> > stable should this interface be? Can't we deal with this when actually
> > implementing NUMA aware ballooning and add stuff at than point, if
> > necessary?
> >
> The risk would be any new guests with extended get_vnumainfo interface
> won't be able to run on old hypervisor (4.5) without proper versioning.
>
Right.
> So basically we have three choices:
> 1. Expose vnode_to_pnode in hypercall interface.
> 2. Expose the mapping in xenstore.
> 3. Don't expose anything, everything happens automagically without guest
> knowing anything.
>
> I'm fine with any of those three. However, Jan suggested in that one
> year old thread it would be wrong for the guest to know the mapping, so
> I think he implicitly voted for the third option.
>
Option 3 is the best IMO too. The guest, ideally, should know nothing
about how Xen mapped its virtual NUMA nodes onto the host RAM.
The question here is how effective that is. As of now, it's quite hard
to judge whether we'll be able to do everything automatically, I think.
I read your proposal, and it looks sensible, I'm just saying it's hard
to be conclusive at this stage.
> I only need to make sure that we don't miss option 1 and release
> incomplete interface for 4.5. That's why I kick off this discussion. If
> we release the interface as it is now and find out we need to expose
> mapping later, we would neither 1) do versioning 2) have yet another
> interface to return mapping.
>
Exactly. Personally, I'd keep the mapping out of the interface we
already have checked in. If it will reveal impossible to do things
completely automatically, I don't think it will be too terrible to add a
new specific hypercall.
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: 181 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:[~2014-11-10 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 19:43 [PATCH for-4.5] xen: vnuma: expose vnode_to_pnode to guest Wei Liu
2014-11-08 19:56 ` Wei Liu
2014-11-10 9:21 ` Jan Beulich
2014-11-10 10:00 ` Wei Liu
2014-11-10 10:51 ` Dario Faggioli
2014-11-10 10:58 ` Jan Beulich
2014-11-10 11:09 ` Wei Liu
2014-11-10 11:21 ` David Vrabel
2014-11-10 11:27 ` Wei Liu
2014-11-10 11:59 ` Dario Faggioli
2014-11-10 11:42 ` Dario Faggioli [this message]
2014-11-10 12:07 ` Wei Liu
2014-11-10 13:43 ` Wei Liu
2014-11-10 15:38 ` 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=1415619727.3717.28.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=JBeulich@suse.com \
--cc=ufimtseva@gmail.com \
--cc=wei.liu2@citrix.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.