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

RE: [Xen-devel] Guest TSC and Xen (Intel and AMD feedback please)


  • To: <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Tue, 8 Jul 2008 09:38:51 +0800
  • Cc: "Zhang, Li" <li.zhang@xxxxxxxxx>
  • Delivery-date: Mon, 07 Jul 2008 18:40:14 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcjboIivPTuddHlLSIGPaPhte5VM5wASModQADA1FBAAMHiVIAAjyGRgAKf/8qA=
  • Thread-topic: [Xen-devel] Guest TSC and Xen (Intel and AMD feedback please)

>From: Dan Magenheimer [mailto:dan.magenheimer@xxxxxxxxxx] 
>Sent: 2008年7月5日 1:32
>
>> >Is this something that you (or Intel in general) could look at?
>> >I would be happy to participate but I don't think I understand
>> >VT well enough.  Once the trap occurs, I suppose Xen system time
>> >could be used as the virtual TSC, possibly scaled up.
>> >
>>
>> There should be tiny related to VT, as only turning on some bit to
>> allow RDTSC trapping and then the rest stuff should be common
>> how to handle it. We'll take a look, but can't commit the time due
>> to other scheduled bandwidth. But if you'd like to jump in early
>> we definitely can help with VT side.
>
>If you can post a patch with code that:
>
>1) declares a boolean global variable: softtsc = 0
>2) if the variable is set, a rdtsc instruction in any hvm
>   domain causes a trap
>3) the trap handler just does a physical rdtsc and returns
>
>then I could probably take it from there.

OK, and Li in CC will take a look and bake a patch for you.

Thanks,
Kevin

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


 


Rackspace

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