On Mon, May 24, 2010 at 10:13:40PM +0200, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This allows to communicate potential IRQ coalescing during delivery from
the sink back to the source. Targets that support IRQ coalescing
workarounds need to register handlers that return the
Gleb Natapov wrote:
On Mon, May 24, 2010 at 10:13:40PM +0200, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This allows to communicate potential IRQ coalescing during delivery from
the sink back to the source. Targets that support IRQ coalescing
workarounds need to register
On Tue, May 25, 2010 at 08:31:06AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, May 24, 2010 at 10:13:40PM +0200, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This allows to communicate potential IRQ coalescing during delivery from
the sink back to the source.
Gleb Natapov wrote:
On Tue, May 25, 2010 at 08:31:06AM +0200, Jan Kiszka wrote:
Gleb Natapov wrote:
On Mon, May 24, 2010 at 10:13:40PM +0200, Jan Kiszka wrote:
From: Jan Kiszka jan.kis...@siemens.com
This allows to communicate potential IRQ coalescing during delivery from
the sink back to
From: Jan Kiszka jan.kis...@siemens.com
This allows to communicate potential IRQ coalescing during delivery from
the sink back to the source. Targets that support IRQ coalescing
workarounds need to register handlers that return the appropriate
QEMU_IRQ_* code, and they have to propergate the code
