In any cases CONFIG_KVM always means CONFIG_PREEMPT_NOTIFIERS
is enabled unconditionally so its really pointless.
CC: Gleb Natapov <g...@kernel.org>
CC: Paolo Bonzini <pbonz...@redhat.com>
Signed-off-by: Tiejun Chen <tiejun.c...@intel.com>
---
include/linux/kvm_host.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
index 9564fd7..695f4f3 100644
--- a/include/linux/kvm_host.h
+++ b/include/linux/kvm_host.h
@@ -220,9 +220,7 @@ struct kvm_mmio_fragment {
struct kvm_vcpu {
struct kvm *kvm;
-#ifdef CONFIG_PREEMPT_NOTIFIERS
struct preempt_notifier preempt_notifier;
-#endif
int cpu;
int vcpu_id;
int srcu_idx;
--
1.9.1
--
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
