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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
