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

[Xen-devel] cpuid bit for relaxed timer handling?


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
  • Date: Mon, 23 Feb 2009 13:02:58 +0000
  • Delivery-date: Mon, 23 Feb 2009 05:03:25 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=sjXsuy65g0W5mOB92h+CG76qDlebDEhFgHs95eWeqjHJzieZd6IQdg7EwFDw8vR0JS 0X//x5ebBQwFdRu+9gqOp+kW4sY7ByDDP7Fb1XRSKTGcyq9xuRMV39H25iEzAueCOPk6 J61PvFkD9Yfs0KCLDdKDr9y/6VElyza78H5rk=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,

I understand that with Xen 3.4 viridian=1 can be specified in the
configugration file to enable viridian support, one of the effects of
which is to set a cpuid bit to enable relaxed timers, I was wondering
if the same bit could be set using the cpuid= setting on older
versions of Xen?

I run Xen 3.2.1 and find that under heavy load my Windows 2008 and
Vista VM's will BSOD with CLOCK_WATCHDOG_TIMEOUT (101), this is pretty
inconvenient on its own but if the VM has a pci passthrough device the
entire system will lock up when this happens, the same lockup happens
if I destroy a VM which has a passthrough device.

I have tried running Xen unstable but when I install gplpv drivers my
windows vm's BSOD with a 7E, I really need the performance boost of
gplpv drivers or I would simply run unstable with no pv drivers.

Andy

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