WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH] per vcpu vhpt

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] per vcpu vhpt
From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date: Mon, 9 Oct 2006 17:59:46 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 09 Oct 2006 03:01:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbrhDnPUCuHFV3LTo66NGIvamv68wAAG21A
Thread-topic: [Xen-ia64-devel] [PATCH] per vcpu vhpt
>
>That makes sense.
>The option 1 is difficult because the vhpt size(currently 64KB and this
>might be increased in future) is smaller than xen granule size (16MB)
and
>non-current vcpu's case must be handled.
I don't see any issue here, if we use option1, we use identity mapping
for VHPT, and so we can use 16 MB TR mapping, of cause, 64KB VHPT is
covered by this 16M TR.

Anthony


>The option 2 seems preferable.
>
>--
>yamahata

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel