xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin@linux.it>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Andre Przywara <andre.przywara@amd.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 2 of 2 RFC] xl: allow for moving the domain's memory when changing vcpu affinity
Date: Fri, 06 Jul 2012 16:05:50 +0200	[thread overview]
Message-ID: <1341583550.15708.47.camel@Abyss> (raw)
In-Reply-To: <1341581104.32747.43.camel@zakaz.uk.xensource.com>


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

On Fri, 2012-07-06 at 14:25 +0100, Ian Campbell wrote: 
> We could do something cleverer for HVM (or hybrid) guests to migrate
> pages while the guest is live but migrating a page under a PV guest's
> feet requires quiescing it in the style of a migrate.
> 
Which, as we're talking about the same host, means reaching a point
where I have two full copies of the guest memory in RAM, or not?

(Just trying to figure out if I understood things sensibly).

> We could probably manage to make it such that you just need the
> pause/frob/unpause phases without actually writing RAM to disk, 
>
Of course, that was in my e-mail too (it's about the above that I'm not
100% sure...).

> and that
> infrastructure might be useful for other reasons I suppose. 
>
Definitely.

Thanks and Regards,
Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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

  parent reply	other threads:[~2012-07-06 14:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06  9:54 [PATCH 0 of 2 RFC] xl: move domeins among NUMA nodes Dario Faggioli
2012-07-06  9:54 ` [PATCH 1 of 2 RFC] xl: parse extra_config options even when restoring Dario Faggioli
2012-07-06  9:54 ` [PATCH 2 of 2 RFC] xl: allow for moving the domain's memory when changing vcpu affinity Dario Faggioli
2012-07-06 12:53   ` George Dunlap
2012-07-06 13:25     ` Ian Campbell
2012-07-06 13:30       ` George Dunlap
2012-07-06 13:38         ` Ian Campbell
2012-07-06 14:05       ` Dario Faggioli [this message]
2012-07-06 14:07         ` George Dunlap
2012-07-06 14:42         ` Ian Campbell
2012-07-06 13:57     ` Dario Faggioli
2012-07-06 14:04       ` George Dunlap
2012-07-06 14:14         ` 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=1341583550.15708.47.camel@Abyss \
    --to=raistlin@linux.it \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andre.przywara@amd.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yang.z.zhang@intel.com \
    /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).