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] Re: [PATCH 12/13] Nested Virtualization: vram

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 12/13] Nested Virtualization: vram
From: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Date: Mon, 13 Sep 2010 14:16:41 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Delivery-date: Mon, 13 Sep 2010 06:17:16 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <201009081747.28298.Christoph.Egger@xxxxxxx>
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: <201009011717.34746.Christoph.Egger@xxxxxxx> <20100908150735.GB23487@xxxxxxxxxxxxxxxxxxxxxxx> <201009081747.28298.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
At 16:47 +0100 on 08 Sep (1283964447), Christoph Egger wrote:
> On Wednesday 08 September 2010 17:07:35 Tim Deegan wrote:
> > Hi,
> >
> > Is this needed as part of the nested-HVM series or just an independent
> > interface change?
> This is an independent interface change.
> It is not needed to make nested-HVM work in general but it is part of
> a larger change to make log dirty code nested virtualization aware.

Ah; does the current nested-SVM patchset break logdirty?

I don't think making the vram structures per-P2M is the best approach.
We're never going to have more than one vram area to track per guest so
it can just operate on the host-p2m, like it does already.

In general, the log-dirty code operates on N1 pfns, and we won't want a
per-p2m log-dirty bitmap either; we'd only have to fold them together to
use them in the tools.



Tim Deegan <Tim.Deegan@xxxxxxxxxx>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd.  (Company #02937203, SL9 0BG)

Xen-devel mailing list