|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api |
Date: | Thu, 21 May 2009 17:37:45 +0300 |
User-agent: | Thunderbird 2.0.0.21 (X11/20090320) |
Paul Brook wrote:
On Thursday 21 May 2009, Avi Kivity wrote:Paul Brook wrote:which is a trivial wrapper around stl_phys.OK, but I'm adding another level of indirection in the middle, to allow us to tie in a kvm backend.kvm has no business messing with the PCI device code.kvm has a fast path for irq injection. If qemu wants to support it we need some abstraction here.Fast path from where to where? Having the PCI layer bypass/re-implement the APIC and inject the interrupt directly into the cpu core sounds a particularly bad idea.
kvm implements the APIC in the host kernel (qemu upstream doesn't support this yet). The fast path is wired to the in-kernel APIC, not the cpu core directly.
The idea is to wire it to UIO for device assignment, to a virtio-device implemented in the kernel, and to qemu.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |