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-devel

[Xen-devel] Xen/ia64 - global or per VP VHPT

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>, "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Subject: [Xen-devel] Xen/ia64 - global or per VP VHPT
From: "Yang, Fred" <fred.yang@xxxxxxxxx>
Date: Thu, 28 Apr 2005 22:56:32 -0700
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, ipf-xen <ipf-xen@xxxxxxxxx>
Delivery-date: Fri, 29 Apr 2005 05:56:17 +0000
Envelope-to: www-data@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: AcVKfesR741jQGkzQvWmdNAbNvskDgAAPPdQAAnH97AAJJJm8AAGJlmgACr730AABzFgcAAYTImw
Thread-topic: Xen/ia64 - global or per VP VHPT
Magenheimer, Dan (HP Labs Fort Collins) wrote:
> Hi Eddie --
>>> I see what you mean about vMMU.  Is it ifdef'd or
>>> a runtime choice?  I'd like to be able to do some
>>> comparisons of a global lVHPT vs a per-domain lVHPT.
>> Besides performance, global VHPT is hard to support multiple
>> page size case like Dom1 uses 16KB default page size while
>> DOM2 uses 4K page size. Also once a VM set rr.ps to a new
>> value, I guess you need to purge the whole VHPT that cause
>> serious problem when the scalability becomes large.
> 
> This is not as much of an issue for paravirtualized domains
> as a minimum page size can be specified.  Also rr.ps
> can be virtualized (and in fact is virtualized in the
> current implementation).
With a single  global VHPT and force the same page size limitation, it
means all the Domaons must be paravirtualized to a hard defined pag
size; this is definitely to limit the capability of the Xen/ia64.   Will
this also imply only certain version of the Domains can run on a same
platform?
What will be the scability issue with a single VHPT table?  Imaging
multi-VP/Multi-LP, all the LPs walking on the same table, you would need
to global purge or send IPI to all processor for purge a single entry.
Costly! 
> 
> I agree that purging is a problem, however Linux does not
> currently change page sizes frequently.
Again, I hope we are not limiting only one OS version to run on this
Xen/ia64.  I believe Linux also needs to purge entries other than page
size changes!
Through per-VP VHPT and VT-I feature of ia64, we can expend Xen/ia64
capability to enable multiple unmodified OS run on Xen/ia64 without
knowing what the page size the Domain is using.  

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Xen/ia64 - global or per VP VHPT, Yang, Fred <=