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] RFC: [0/2] Remove netloop by lazy copying in netback

To: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Tue, 27 Mar 2007 11:40:00 +0100
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, Xen Development Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 27 Mar 2007 03:39:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070327102524.GA25582@xxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdwXET7g0jDE9xPEdu1BgAX8io7RQ==
Thread-topic: [Xen-devel] RFC: [0/2] Remove netloop by lazy copying in netback
User-agent: Microsoft-Entourage/
On 27/3/07 11:25, "Herbert Xu" <herbert@xxxxxxxxxxxxxxxxxxx> wrote:

> Actually we can just mark the PTEs as not present in that case.  The
> hypervisor can then mark the PTEs as present on the first fault.
> Just as grant table operations currently work on virtual addresses for
> non-translated guests and physical addresses for translated guests,
> such an operation would work on PTEs for non-translated guests and
> p2m entries for translated guests.

Yeah, but: how does Xen efficiently work out whether a not-present fault is
due to a lazy grant mapping and, if so, what it is that needs to be demand
mapped? PV guests can store what they like in not-present pagetable entries.
Perhaps we could make use of reserved bits in ptes instead (not that there
are any in non-pae x86, but I'd very much like to obsolete non-pae x86 Xen
after 3.0.5 anyway -- I don't think anyone actually ships a product with
non-pae bits).

 -- Keir

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>