On Wed, Mar 06, 2013 at 01:20:39PM +0100, Alexander Graf wrote:
> > The problem would only start if KVM_SET_IRQCHIP_TYPE (new name of
> > KVM_CREATE_IRQCHIP_ARGS) forced you to later call KVM_CREATE_DEVICE.
>
> Ah, I see. I don't see why it would. The fact that there is a "LAPIC" doesn't
> mean that the per-vcpu SET_INTERRUPT ioctl stops working. So if
> SET_IRQCHIP_TYPE(!none) breaks user-space interrupt controller emulation I
> would consider that a bug.
>
For x86 this is the case though. I do not see how it can't be. If
LAPIC is emulated in userspace SET_INTERRUPT is used to pass IRQ
vector that should be handled as a result of LAPIC emulation.
--
Gleb.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
