From: Peter Maydell <peter.maydell@linaro.org>
Date: Thu, 26 Jul 2012 14:35:17 +0000 (+0100)
Subject: kvm: Add documentation comment for kvm_irqchip_in_kernel()
X-Git-Tag: qemu-xen-4.3.0-rc1~748^2
X-Git-Url: http://xenbits.xensource.com/gitweb?a=commitdiff_plain;h=96fda35ac477e954eee989d6a3ae9e686cc361d6;p=qemu-upstream-4.5-testing.git

kvm: Add documentation comment for kvm_irqchip_in_kernel()

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>
Signed-off-by: Avi Kivity <avi@redhat.com>
---

diff --git a/kvm.h b/kvm.h
index 444ed2e70..5b8f58881 100644
--- a/kvm.h
+++ b/kvm.h
@@ -31,6 +31,17 @@ extern bool kvm_gsi_routing_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)
 
 /**