diff options
author | Peter Maydell <peter.maydell@linaro.org> | 2012-07-25 13:41:40 +0100 |
---|---|---|
committer | Peter Maydell <peter.maydell@linaro.org> | 2012-07-25 13:41:40 +0100 |
commit | fd817c062f49dc9d45f6d7291a906d042e329244 (patch) | |
tree | 01ce0a4b2b3cfd01f2c3eadace67781bbfd427f9 | |
parent | 3e4a481d67b767370ee90188556b121bfe2c49cb (diff) |
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.h | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -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: |