qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Re: [Bug 599958] Re: Timedrift problems with Win7: hpet


From: Avi Kivity
Subject: Re: [Qemu-devel] Re: [Bug 599958] Re: Timedrift problems with Win7: hpet missing time drift fixups
Date: Mon, 05 Jul 2010 11:47:44 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100430 Fedora/3.0.4-3.fc13 Thunderbird/3.0.4

On 07/05/2010 10:36 AM, Jan Kiszka wrote:

Assumes that CPU with
lowest index is BSP (that one we can actually guaranty if we want
to).
Well, the generic solution would be returning a bitmap of the CPUs that
were affected, but this is impractical. However, at least x86 should be
fine with the information "state change also on BSP", e.g. like this:
  0 - state change on one or more CPUs, none of them is the BSP
  1 - state change on BSP (and possible more CPUs)

What about ack notifiers? Ask the APIC to notify you when an interrupt is acked. That allows you to track the BSP, all cpus, or some subset. Masking can be seen at the irq controller level.

It's more involved, but provides more information.



--
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]