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

[Xen-ia64-devel] vTLB support

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] vTLB support
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Tue, 3 May 2005 13:01:55 +0800
Delivery-date: Tue, 03 May 2005 05:02:01 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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: AcVPnTny450UmdJrT5mS9xLEjZls6A==
Thread-topic: vTLB support
Dan:
        I am worring about the vTLB support base on current
implementation. 
        The current implementation as you mentioned use:
        TR_ENTRY itrs[NITRS];
        TR_ENTRY dtrs[NDTRS];
        TR_ENTRY itlb;  
        TR_ENTRY dtlb;
        and you mentioned to use machine TR for hypercall shared page.

        I am thinking the way to support foreignmap and mmio shared page
base on current implementation. The foreignmap is probably per domain
16GB memory space map. If you want to add another variable like
"TR_ENTRY foreignmap[MAX_DOMAINS]" and "TR_ENTRY
mmio_shared_page[MAX_DOMAINS], I think the guest TLB walk will be too
expansive. Same situation for TC insert and purge. (BTW, current code is
not checking for the overlap of guest TLB at time of insert.)
        If you are willing, my implementation can be one solution. I
mainly use a HASH+collision chain for vTLB and VHPT. vTLB and VHPT use
same code but different instance. If you want to use global VHPT, you
can just create one instance for that. We don't need to worry about how
to support both.
Eddie

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

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