[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Hardware interrupts
From: |
Paul Brook |
Subject: |
Re: [Qemu-devel] Hardware interrupts |
Date: |
Mon, 17 Jul 2006 19:44:02 +0100 |
User-agent: |
KMail/1.9.3 |
> "In order to be faster, QEMU does not check at every basic block if an
> hardware interrupt is pending. Instead, the user must asynchrously call a
> specific function to tell that an interrupt is pending. This function
> resets the chaining of the currently executing basic block. It ensures that
> the execution will return soon in the main loop of the CPU emulator. Then
> the main loop can test if the interrupt is pending and handle it."
> What means "the user must asynchrously call a specific function..."?
>
> In which sense "user must"?
Whoever wants to raise the interrupt.
> Which "Specific function"?
Usually pic_set_irq_new.
I recommend you look at how the existing hardware devices are implemented.
That should answer most of your questions. I'd start with something simple
like serial.c or pl050.c
Paul