Thread (1 message) 1 message, 1 author, 2009-05-21

Re: [Qemu-devel] [PATCH] qemu: msi irq allocation api

From: Avi Kivity <hidden>
Date: 2009-05-21 14:54:57

Paul Brook wrote:
quoted
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.
    
I still don't see why you're trying to bypass straight from the pci layer to 
the apic. Why can't you just pass the apic MMIO writes to the kernel? You've 
presumably got to update the apic state anyway.
  
The fast path is an eventfd so that we don't have to teach all the 
clients about the details of MSI.  Userspace programs the MSI details 
into kvm and hands the client an eventfd.  All the client has to do is 
bang on the eventfd for the interrupt to be queued.  The eventfd 
provides event coalescing and is equally useful from the kernel and 
userspace, and can be used with targets other than kvm.

-- 
error compiling committee.c: too many arguments to function
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help