All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Elena Ufimtseva <ufimtseva@gmail.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Jan Beulich <JBeulich@suse.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:59:02 +0100	[thread overview]
Message-ID: <1415620742.3717.39.camel@Abyss> (raw)
In-Reply-To: <20141110112751.GB28360@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1353 bytes --]

On Mon, 2014-11-10 at 11:27 +0000, Wei Liu wrote:
> On Mon, Nov 10, 2014 at 11:21:40AM +0000, David Vrabel wrote:
> > On 10/11/14 11:09, Wei Liu wrote:
> > > 
> > > 3. Don't expose anything, everything happens automagically without guest
> > >    knowing anything.
> > 
> > This.  The vnode to pnode mapping can change on a save/restore.
> 
> I don't think this is the most decisive reasoning of this issue. The
> other two options can also deal with this -- just retrieve the
> up-to-date versions after migration.
> 
IMO, what's needed is an "on demand" "translation service". The guest
should not store the result of such translation and rely on it.

The opposite, actually: when ballooning up (i.e., the only legittimate
use case of this "service" I can think of right now), it should be
possible to let the hypervisor know from what physical NUMA node we want
a page, basing on which vnode such page belongs to.

This is probably another argument for not using option 1, and for going
for 3, if possible, or with something different, if not.

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

  reply	other threads:[~2014-11-10 11:59 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 [this message]
2014-11-10 11:42         ` Dario Faggioli
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=1415620742.3717.39.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.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.