linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: n.nikolaev@virtualopensystems.com (Nikolay Nikolaev)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 4/5] ARM: enable linking against eventfd and irqchip
Date: Mon, 24 Nov 2014 23:27:06 +0200	[thread overview]
Message-ID: <20141124212706.10605.50148.stgit@i3820> (raw)
In-Reply-To: <20141124212240.10605.46770.stgit@i3820>

This enables compilation of the eventfd feature on ARM.

Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
---
 arch/arm/kvm/Kconfig  |    1 +
 arch/arm/kvm/Makefile |    2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/arch/arm/kvm/Kconfig b/arch/arm/kvm/Kconfig
index 466bd29..a4b0312 100644
--- a/arch/arm/kvm/Kconfig
+++ b/arch/arm/kvm/Kconfig
@@ -20,6 +20,7 @@ config KVM
 	bool "Kernel-based Virtual Machine (KVM) support"
 	select PREEMPT_NOTIFIERS
 	select ANON_INODES
+	select HAVE_KVM_EVENTFD
 	select HAVE_KVM_CPU_RELAX_INTERCEPT
 	select KVM_MMIO
 	select KVM_ARM_HOST
diff --git a/arch/arm/kvm/Makefile b/arch/arm/kvm/Makefile
index 443b8be..539c1a5 100644
--- a/arch/arm/kvm/Makefile
+++ b/arch/arm/kvm/Makefile
@@ -15,7 +15,7 @@ AFLAGS_init.o := -Wa,-march=armv7-a$(plus_virt)
 AFLAGS_interrupts.o := -Wa,-march=armv7-a$(plus_virt)
 
 KVM := ../../../virt/kvm
-kvm-arm-y = $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o
+kvm-arm-y = $(KVM)/kvm_main.o $(KVM)/coalesced_mmio.o $(KVM)/eventfd.o
 
 obj-y += kvm-arm.o init.o interrupts.o
 obj-y += arm.o handle_exit.o guest.o mmu.o emulate.o reset.o

  parent reply	other threads:[~2014-11-24 21:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 21:26 [RFC PATCH 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Nikolay Nikolaev
2014-11-24 21:26 ` [RFC PATCH 1/5] KVM: redesing kvm_io_bus_ API to pass VCPU structure to the callbacks Nikolay Nikolaev
2014-11-26 17:03   ` Eric Auger
2014-11-24 21:26 ` [RFC PATCH 2/5] ARM: on IO mem abort - route the call to KVM MMIO bus Nikolay Nikolaev
2014-11-27 10:19   ` Eric Auger
2014-11-29 11:28   ` Christoffer Dall
2014-12-05 12:06     ` Nikolay Nikolaev
2015-01-12 16:21       ` Eric Auger
2015-01-23 22:38         ` Nikolay Nikolaev
2014-11-29 11:29   ` Christoffer Dall
2014-11-24 21:26 ` [RFC PATCH 3/5] KVM: ARM VGIC add kvm_io_bus_ frontend Nikolay Nikolaev
2014-11-27 10:51   ` Eric Auger
2014-11-29  7:14   ` Shannon Zhao
2014-11-29 13:58     ` Nikolay Nikolaev
2014-11-29 11:29   ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-11-29 13:54     ` Nikolay Nikolaev
2014-12-05 12:10       ` Nikolay Nikolaev
2014-12-08 10:51         ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-11-24 21:27 ` Nikolay Nikolaev [this message]
2014-11-26 16:58   ` [RFC PATCH 4/5] ARM: enable linking against eventfd and irqchip Eric Auger
2014-11-29  7:18   ` Shannon Zhao
2014-11-29 13:49     ` Nikolay Nikolaev
2014-11-29 14:32       ` Christoffer Dall
2014-11-29 11:29   ` Christoffer Dall
2014-12-05 12:14     ` Nikolay Nikolaev
2014-11-24 21:27 ` [RFC PATCH 5/5] ARM: enable KVM_CAP_IOEVENTFD Nikolay Nikolaev
2014-11-27 11:01 ` [RFC PATCH 0/5] ARM: KVM: Enable the ioeventfd capability of KVM on ARM Eric Auger

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=20141124212706.10605.50148.stgit@i3820 \
    --to=n.nikolaev@virtualopensystems.com \
    --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).