Re: [Xen-devel] [PATCH] new hvm platform vhpet enable parameter

[Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>]

HPET is also advertised in the ACPI tables which would need to be gated.
Should be called vhpet not hpet as the 'v' is rather redundant.

Why would we want to do the same for pmtimer? Is it inaccurate?

 -- Keir

On 7/2/08 17:46, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> HVM domains currently always have a virtual hpet (high-precision event timer)
> enabled.  This patch adds an hvm platform variable "vhpet" to enable/disable
> virtualization of the hpet for a guest.
> 
> Default is off (no vhpet) because vhpet is currently less accurate in keeping
> time than PIT (because no timer_mode adjustments), and because AFAICT VMware
> still doesn't implement virtual hpet.
> 
> A similar patch to enable/disable pmtimer is also needed but I thought
> I'd post this one for discussion first.
> 
> This patch applies against and was tested with xen-3.1-testing.
> 
> Signed-off-by: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
> 
> ===================================
> If Xen could save time in a bottle / then clocks wouldn't virtually skew /
> It would save every tick / for VMs that aren't quick /
> and Xen then would send them anew
> (with apologies to the late great Jim Croce)
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



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