This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Tracking guest pages modified by qemu-dm / backend

To: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Tracking guest pages modified by qemu-dm / backend
From: AP <apxeng@xxxxxxxxx>
Date: Fri, 24 Jun 2011 10:22:21 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 24 Jun 2011 10:23:13 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=rM31RcrqJEZmEuMmYS2Wh6sm0T79b0yyNSMxFGqIVIw=; b=PX6T2EqFQv2mNwZteIWiawkvMzlxfE0MFiIMv4rAzJMY1a9mA+SQvJzOVa5AhI3JH+ 7p43ASWb5NLxQo4EMtIq0riK24t/4qxHZQslrYtOBULb0u43Fsx4sx8woEIfG+BVDBO9 kfImhcxIFC3j9ZY99wCfuWig+77aE/DRijj7Y=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110624084010.GW17634@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BANLkTimiagS5cXj0nOPkCzxMzZMaZH724w@xxxxxxxxxxxxxx> <20110622084953.GR17634@xxxxxxxxxxxxxxxxxxxxxxx> <BANLkTi=xKF79x-5pg2us7cjZ9-K6kzKfgA@xxxxxxxxxxxxxx> <20110624084010.GW17634@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jun 24, 2011 at 1:40 AM, Tim Deegan <Tim.Deegan@xxxxxxxxxx> wrote:
> At 11:06 -0700 on 23 Jun (1308827188), AP wrote:
>> On Wed, Jun 22, 2011 at 1:49 AM, Tim Deegan <Tim.Deegan@xxxxxxxxxx> wrote:
>> > Hi,
>> >
>> > At 15:43 -0700 on 21 Jun (1308671006), AP wrote:
>> >> Consider an HVM domain with EPT. When qemu-dm, backend or any other
>> >> device model modifies DomU memory (like on a disk read or packet
>> >> received), how does Xen track the pages that have been modified? For
>> >> example, when an DomU is being migrated while IO is occurring.
>> >
>> > Backends use grant tables to map guest memory; the granted pages are
>> > marked dirty when the backend disconnects.  Qemu-dm uses the
>> > HVMOP_modified memory hypercall to tell Xen that it's written to
>> > the guest's memory.
>> From what I see for EPT/HAP, log dirty is turned on only during domain
>> save.
> It's also used to track just the virtual framebuffer so qemu can avoid
> having to compute which parts of the screen to send over VNC.
> But for general memory it's only used during save, because there's no
> need for it otherwise.  If you're confused about that maybe you should
> read the original paper on Xen live migration:
> http://www.cl.cam.ac.uk/research/srg/netos/papers/2005-nsdi-migration.pdf

Sorry I think I did not phrase my question well. What I was not able
to understand was how / where the granted pages were being marked
dirty w.r.t EPT after the backend disconnects.


Xen-devel mailing list