[Top][All Lists]

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

Re: [Qemu-devel] How Qemu timer interrupts code emulation?

From: Bastian Koppelmann
Subject: Re: [Qemu-devel] How Qemu timer interrupts code emulation?
Date: Sat, 23 May 2015 01:03:20 +0200
User-agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

On 05/22/2015 06:26 PM, Nguyen Anh Quynh wrote:

On Sat, May 23, 2015 at 12:13 AM, Peter Maydell <address@hidden> wrote:
On 22 May 2015 at 16:36, Jun Koi <address@hidden> wrote:
> In general, we would have timer & code execution run in parallel,

No code has to actually run when there's an active timer;
the event loop thread mostly sits blocked waiting for
something interesting to happen (io or a timer firing).
When it does then the event loop thread will call the
generic timer code, which will call the callback function
for that timer. Typically this is inside the device model
for whatever timer the hardware you're modelling is. It
will then (assuming it really wants to create a simulated
interrupt) call qemu_irq_set()

What is the exact name of this function? There is no such qemu_irq_set()
in the latest 2.3.0 source.

Peter just got it switched around, it's qemu_set_irq() in include/hw/irq.h.


reply via email to

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