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

RE: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization


  • To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
  • From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
  • Date: Tue, 3 May 2005 14:51:51 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 03 May 2005 06:55:32 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcVNYTbiS1g8dJcOT9aDwf6uWGSJAwAnrY6QAA5pBSAAEa0J4AAKTeQAAARAyhAAPGDw4A==
  • Thread-topic: [Xen-ia64-devel] machine ITM = nearest guest ITM vs. full guesttime virtualization

Magenheimer, Dan (HP Labs Fort Collins) wrote:
> 
> If you think of the "Xen ITC" as the official ITC, domain switch
> from A to B requires adding the offset of domainA to return to
> Xen ITC, then subtracting the offset of domainB to obtain domainB's
> ITC.
Without tracking last ITC, the guest time IRQ may be missed or multiple
triggered like the bug kevin fix for you 1-2 months ago.
> 
> I think this works and is very simple... but as I said, this hasn't
> been tested because Linux doesn't do it.
Yes, both are not a big cake, but keeping 2 sets of code may cause
future support issues.
eddie

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