On 05/28/2010 01:19 AM, Jan Kiszka wrote:
Still, this does not answer:
- How do you want to detect lost timer ticks?
Your (and Gleb's) approach: during injection
An alternative: during guest ack
The normal pattern is inj/ack/inj/ack; if we see inj/inj/inj we know the
guest isn't keeping up.
- What subsystem(s) keeps track of the backlog?
Clearly, the clock chip (hpet/rtc/pit).
With the alternative approach, the clock emulation requests that acks be
reported via a qemu_irq interface.
- And depending on the above: How to detect at all that a specific IRQ
is a timer tick?
Clearly, a blocker unless the clock is responsible for timekeeping.
--
error compiling committee.c: too many arguments to function
