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

[Xen-ia64-devel] a potential issue in set/get-rse-reg function


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Tue, 13 Sep 2005 17:07:36 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 13 Sep 2005 09:05:15 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcW4QpVmi9T1OrvAQmOVqmucMzXuaw==
  • Thread-topic: a potential issue in set/get-rse-reg function

Dan,

In current implementation, Guest stack register of current guest
function can be saved in hypervisor backing store or/and guest backing
store, if some saved in guest backing store, set/get-rse-reg will
directly access guest backing store, at this time, tlb miss may happen.
But tlb miss handler only search guest vhpt not guest page table, that
means it is possible hypervisor can't handle this tlb miss and inject
tlb miss to guest kernel, at this situation, I think hypervisor can't
inject tlb miss to guest kernel. 
One explicit solution is in ivt.S set rse to lazy mode before do 'cover'
to make sure guest stack register of current guest function are all
saved in hypervisor backing store. Yes this solution will penalize
performance, but just a little, because there are only about ten
assembly instructions between 'cover' and 'mov ar.rse=0' in current
implementation.
What's your opinion?

Thanks
Anthony.

_______________________________________________
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®.