On Sun, 1 Jun 2008, Marcelo Tosatti wrote:
> On Sun, Jun 01, 2008 at 06:34:27PM +0200, Thomas Gleixner wrote:
>
> A sysfs entry sounds fine and much simpler. Should probably be a generic
> clocksource interface (so userspace can read any available clocksource)
> rather than acpi_pm specific.
Agreed.
> > return clocksource_acpi_pm.read == acpi_pm_read;
> >
> > So we don't need reliable_pmtimer at all.
>
> For KVM's use case, we'd rather not allow direct pmtimer access if the
> host has an unreliable (buggy) chipset.
well, "return clocksource_acpi_pm.read == acpi_pm_read;" is supposed
to do that just without an additional variable "reliable_pmtimer" :)
> But then, I doubt any of those older affected chipsets have HW
> virtualization support, so it shouldnt be an issue.
It's exactly one old crappy chipset, which definitely has no HW virt
support and therefor we just can use read_pmtmr() w/o checking for
reliable or not.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
