aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Maydell <peter.maydell@linaro.org>2012-07-25 13:41:40 +0100
committerPeter Maydell <peter.maydell@linaro.org>2012-07-25 13:41:40 +0100
commitfd817c062f49dc9d45f6d7291a906d042e329244 (patch)
tree01ce0a4b2b3cfd01f2c3eadace67781bbfd427f9
parent3e4a481d67b767370ee90188556b121bfe2c49cb (diff)
downloadqemu-arm-q-l-kvm-x86isms.tar.gz
kvm: Add documentation comment for kvm_irqchip_in_kernel()q-l-kvm-x86isms
Now we've cleared out the architecture-independent uses of kvm_irqchip_in_kernel(), we can add a doc comment describing what it means. Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
-rw-r--r--kvm.h11
1 files changed, 11 insertions, 0 deletions
diff --git a/kvm.h b/kvm.h
index 77841fc1e7..a865c12217 100644
--- a/kvm.h
+++ b/kvm.h
@@ -30,6 +30,17 @@ extern bool kvm_msi_via_irqfd_allowed;
#if defined CONFIG_KVM || !defined NEED_CPU_H
#define kvm_enabled() (kvm_allowed)
+/**
+ * kvm_irqchip_in_kernel:
+ *
+ * Returns: true if the user asked us to create an in-kernel
+ * irqchip via the "kernel_irqchip=on" machine option.
+ * What this actually means is architecture and machine model
+ * specific: on PC, for instance, it means that the LAPIC,
+ * IOAPIC and PIT are all in kernel. This function should never
+ * be used from generic target-independent code: use one of the
+ * following functions or some other specific check instead.
+ */
#define kvm_irqchip_in_kernel() (kvm_kernel_irqchip)
/**
* kvm_async_interrupt_injection: