linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 1/6] KVM: arm/arm64: select IRQ_BYPASS_MANAGER
Date: Mon,  6 Jul 2015 14:11:27 +0200	[thread overview]
Message-ID: <1436184692-20927-2-git-send-email-eric.auger@linaro.org> (raw)
In-Reply-To: <1436184692-20927-1-git-send-email-eric.auger@linaro.org>

Select IRQ_BYPASS_MANAGER when CONFIG_KVM is set

Signed-off-by: Eric Auger <eric.auger@linaro.org>

---
v1 -> v2:
- also set IRQ_BYPASS_MANAGER for arm64
---
 arch/arm/kvm/Kconfig   | 1 +
 arch/arm64/kvm/Kconfig | 1 +
 2 files changed, 2 insertions(+)

diff --git a/arch/arm/kvm/Kconfig b/arch/arm/kvm/Kconfig
index bfb915d..7d38d25 100644
--- a/arch/arm/kvm/Kconfig
+++ b/arch/arm/kvm/Kconfig
@@ -31,6 +31,7 @@ config KVM
 	select KVM_VFIO
 	select HAVE_KVM_EVENTFD
 	select HAVE_KVM_IRQFD
+	select IRQ_BYPASS_MANAGER
 	depends on ARM_VIRT_EXT && ARM_LPAE && ARM_ARCH_TIMER
 	---help---
 	  Support hosting virtualized guest machines.
diff --git a/arch/arm64/kvm/Kconfig b/arch/arm64/kvm/Kconfig
index bfffe8f..d1922b4 100644
--- a/arch/arm64/kvm/Kconfig
+++ b/arch/arm64/kvm/Kconfig
@@ -31,6 +31,7 @@ config KVM
 	select KVM_VFIO
 	select HAVE_KVM_EVENTFD
 	select HAVE_KVM_IRQFD
+	select HAVE_KVM_IRQFD
 	---help---
 	  Support hosting virtualized guest machines.
 
-- 
1.9.1

  reply	other threads:[~2015-07-06 12:11 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 12:11 [RFC v2 0/6] IRQ bypass manager and irqfd consumer Eric Auger
2015-07-06 12:11 ` Eric Auger [this message]
2015-07-06 12:24   ` [RFC v2 1/6] KVM: arm/arm64: select IRQ_BYPASS_MANAGER Paolo Bonzini
2015-07-06 12:11 ` [RFC v2 2/6] VFIO: platform: " Eric Auger
2015-07-06 12:11 ` [RFC v2 3/6] irq: bypass: Extend skeleton for ARM forwarding control Eric Auger
2015-07-06 12:27   ` Paolo Bonzini
2015-07-06 15:35     ` Eric Auger
2015-07-06 15:57       ` Paolo Bonzini
2015-07-06 17:09         ` Eric Auger
2015-07-06 17:41           ` Paolo Bonzini
2015-07-07  7:10             ` Eric Auger
2015-07-07  8:58               ` Paolo Bonzini
2015-07-07 10:58   ` Wu, Feng
2015-07-07 11:00     ` Paolo Bonzini
2015-07-07 11:13       ` Wu, Feng
2015-07-07 11:13         ` Paolo Bonzini
2015-07-07 11:18           ` Wu, Feng
2015-07-07 11:21             ` Paolo Bonzini
2015-07-07 11:24               ` Wu, Feng
2015-07-07 11:33                 ` Wu, Feng
2015-07-07 13:22                   ` Paolo Bonzini
2015-07-06 12:11 ` [RFC v2 4/6] KVM: create kvm_irqfd.h Eric Auger
2015-07-06 12:11 ` [RFC v2 5/6] KVM: introduce kvm_arch functions for IRQ bypass Eric Auger
2015-07-06 12:11 ` [RFC v2 6/6] KVM: eventfd: add irq bypass consumer management Eric Auger
2015-07-07  8:47   ` Wu, Feng
2015-07-07  9:05     ` Eric Auger
2015-07-07  9:13       ` Wu, Feng
2015-07-07 17:17 ` [RFC v2 0/6] IRQ bypass manager and irqfd consumer Alex Williamson
2015-07-09 12:28   ` Joerg Roedel
2015-07-09 14:13     ` Alex Williamson
2015-07-09 14:38       ` Paolo Bonzini
2015-07-09 15:34         ` Joerg Roedel
2015-07-09 16:06           ` Alex Williamson
2015-07-24  1:27 ` Wu, Feng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1436184692-20927-2-git-send-email-eric.auger@linaro.org \
    --to=eric.auger@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).