Note: groups.io will be down for maintenance this evening, starting at 11pm Pacific Time (6am Tuesday 8/3/2020 UTC), for up to two hours.
Roger Pau Monné
On Thu, Aug 08, 2019 at 03:26:41PM +0100, Anthony PERARD wrote:
On Thu, Aug 08, 2019 at 03:44:23PM +0200, Roger Pau Monné wrote:But after your series both PVH and HVM will use the lapic timerOn Thu, Aug 08, 2019 at 02:28:32PM +0100, Anthony PERARD wrote:So EDKII doesn't have that capability, FSBClock is a build time valueOn Wed, Aug 07, 2019 at 05:54:51PM +0200, Roger Pau Monné wrote:I don't think that's part of the HVM/PVH ABI in any way, and if youOn Mon, Jul 29, 2019 at 04:39:38PM +0100, Anthony PERARD wrote:It's hardcoded. Why would you need auto detection when you always run onPcdFSBClock is used by SecPeiDxeTimerLibCpu, the TimerLibI'm kind of surprised that his is not automatically detected?
instead of the ACPI timer, and thus rely on the value of FSBClock?
We could try to find a better way to get time in OvmfXen withoutYes please. As said above lapic frequency is not part of the ABI, so
if we need to use it like that APIC_BUS_CYCLE_NS (currently in
vlapic.h) would have to be moved to a public header.