|
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 12:23:03 +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 12:07 PM, Jan Kiszka wrote:
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.So, if I understand you correctly, an IRQ state change that is ignored due to masking would invoke the ack notifier chain as well?
No - the cpu doesn't ack, no ack notifier. We might need a separate mask notifier. Just add pomodoro sauce.
It's more involved, but provides more information.Well, it requires to establish ack notifier chains in parallel to the existing IRQ delivery routes. Definitely more invasive.
Right, and need to plumb it twice, once for qemu and once for kvm. But my feeling is you get a lot more information out of it. -- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |