[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] vTLB support


  • To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Fri, 6 May 2005 12:23:11 -0700
  • Delivery-date: Fri, 06 May 2005 19:22:43 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVPnTny450UmdJrT5mS9xLEjZls6AAUr96AAKAmGZA=
  • Thread-topic: [Xen-ia64-devel] vTLB support

> -----Original Message-----
> From: Magenheimer, Dan (HP Labs Fort Collins) 
> Sent: Tuesday, May 03, 2005 9:09 AM
> Subject: RE: [Xen-ia64-devel] vTLB support
> 
> You may already understand this but I will explain it
> for others on the list.  This describes the current
> implementation...
> 
> The shared page is at a fixed virtual address in the
> Xen virtual address space (0xf200000000000000).
> The page is persistent for each domain; there is a
> different physical page backing this virtual address
> for each domain.  The mapping is switched at domain
> switch time.  Currently the mapping is placed in a
> physical TR; this need not be the case as long as it
> is guaranteed that Xen never delivers/injects a TLB
> miss to the guest for this address.

A correction on this:  I had forgotten that Xen
itself may need to access the shared page when
psr.ic is off (to implement fast hyperprivops),
so it does need to be pinned in a TR.

Dan

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.