diff options
| author | Peter Maydell | 2012-07-26 16:35:14 +0200 |
|---|---|---|
| committer | Avi Kivity | 2012-08-09 15:16:56 +0200 |
| commit | cc7e0ddf5a2307015eacfac2ac6a6a765898fcc3 (patch) | |
| tree | 9f48e5a70cd18a95d2810c983b3fecba05ae75b3 /kvm-stub.c | |
| parent | kvm: Move kvm_allows_irq0_override() to target-i386, fix return type (diff) | |
| download | qemu-cc7e0ddf5a2307015eacfac2ac6a6a765898fcc3.tar.gz qemu-cc7e0ddf5a2307015eacfac2ac6a6a765898fcc3.tar.xz qemu-cc7e0ddf5a2307015eacfac2ac6a6a765898fcc3.zip | |
kvm: Decouple 'irqfds usable' from 'kernel irqchip'
Instead of assuming that we can use irqfds if and only if
kvm_irqchip_in_kernel(), add a bool to the KVMState which
indicates this, and is set only on x86 and only if the
irqchip is in the kernel.
The kernel documentation implies that the only thing
you need to use KVM_IRQFD is that KVM_CAP_IRQFD is
advertised, but this seems to be untrue. In particular
the kernel does not (alas) return a sensible error if you
try to set up an irqfd when you haven't created an irqchip.
If it did we could remove all this nonsense and let the
kernel return the error code.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Acked-by: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'kvm-stub.c')
| -rw-r--r-- | kvm-stub.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/kvm-stub.c b/kvm-stub.c index f2b0c61983..02e7fe0507 100644 --- a/kvm-stub.c +++ b/kvm-stub.c @@ -20,6 +20,7 @@ KVMState *kvm_state; bool kvm_kernel_irqchip; bool kvm_async_interrupts_allowed; +bool kvm_irqfds_allowed; int kvm_init_vcpu(CPUArchState *env) { |