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] Regarding page table management changes from Xen v1 to X

To: Himanshu Raj <rhim@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Regarding page table management changes from Xen v1 to Xen v2 (and v3)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 26 Apr 2006 18:44:24 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 26 Apr 2006 10:48:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20060426174057.GD27766@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20060426153556.GB27766@xxxxxxxxxxxxx> <d11931952836ca30cdc2dd7a2edb72b1@xxxxxxxxxxxx> <20060426174057.GD27766@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 26 Apr 2006, at 18:40, Himanshu Raj wrote:

Although, same results can be obtained by doing the v1.2 way, i.e. making one
hypercall requesting these 1024 changes, no?


You have to marshal/unmarshal the batched arguments, and insert flushes all over the place to ensure the requests get flushed before Linux next tries to read any of the ptes. So the new method is fewer changes to the guest and no slower for reasonable-sized batches.

 -- Keir

Xen-devel mailing list