From: Yifei Jiang <jiangyifei@huawei.com>
To: <pbonzini@redhat.com>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <aou@eecs.berkeley.edu>
Cc: victor.zhangxiaofeng@huawei.com, zhang.zhanghailiang@huawei.com,
kvm@vger.kernel.org, anup.patel@wdc.com,
linux-kernel@vger.kernel.org, atish.patra@wdc.com,
Yifei Jiang <jiangyifei@huawei.com>,
kvm-riscv@lists.infradead.org, limingwang@huawei.com,
linux-riscv@lists.infradead.org, wu.wubin@huawei.com,
dengkai1@huawei.com
Subject: [RFC 1/2] RISC-V: KVM: enable ioeventfd capability and compile for risc-v
Date: Fri, 24 Jul 2020 16:54:40 +0800 [thread overview]
Message-ID: <20200724085441.1514-2-jiangyifei@huawei.com> (raw)
In-Reply-To: <20200724085441.1514-1-jiangyifei@huawei.com>
Signed-off-by: Yifei Jiang <jiangyifei@huawei.com>
Signed-off-by: Mingwang Li <limingwang@huawei.com>
---
arch/riscv/kvm/Kconfig | 2 ++
arch/riscv/kvm/Makefile | 2 +-
arch/riscv/kvm/vm.c | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/riscv/kvm/Kconfig b/arch/riscv/kvm/Kconfig
index 2356dc52ebb3..95d85d893ab6 100644
--- a/arch/riscv/kvm/Kconfig
+++ b/arch/riscv/kvm/Kconfig
@@ -4,6 +4,7 @@
#
source "virt/kvm/Kconfig"
+source "drivers/vhost/Kconfig"
menuconfig VIRTUALIZATION
bool "Virtualization"
@@ -26,6 +27,7 @@ config KVM
select KVM_MMIO
select HAVE_KVM_VCPU_ASYNC_IOCTL
select SRCU
+ select HAVE_KVM_EVENTFD
help
Support hosting virtualized guest machines.
diff --git a/arch/riscv/kvm/Makefile b/arch/riscv/kvm/Makefile
index b56dc1650d2c..3ad46fe44900 100644
--- a/arch/riscv/kvm/Makefile
+++ b/arch/riscv/kvm/Makefile
@@ -2,7 +2,7 @@
# Makefile for RISC-V KVM support
#
-common-objs-y = $(addprefix ../../../virt/kvm/, kvm_main.o coalesced_mmio.o)
+common-objs-y = $(addprefix ../../../virt/kvm/, kvm_main.o coalesced_mmio.o eventfd.o)
ccflags-y := -Ivirt/kvm -Iarch/riscv/kvm
diff --git a/arch/riscv/kvm/vm.c b/arch/riscv/kvm/vm.c
index 4f2498198cb5..473299e71f68 100644
--- a/arch/riscv/kvm/vm.c
+++ b/arch/riscv/kvm/vm.c
@@ -52,6 +52,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
int r;
switch (ext) {
+ case KVM_CAP_IOEVENTFD:
case KVM_CAP_DEVICE_CTRL:
case KVM_CAP_USER_MEMORY:
case KVM_CAP_SYNC_MMU:
--
2.19.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2020-07-24 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 8:54 [RFC 0/2] Add risc-v vhost-net support Yifei Jiang
2020-07-24 8:54 ` Yifei Jiang [this message]
2020-07-26 12:48 ` [RFC 1/2] RISC-V: KVM: enable ioeventfd capability and compile for risc-v Anup Patel
2020-07-24 8:54 ` [RFC 2/2] RISC-V: KVM: read\write kernel mmio device support Yifei Jiang
2020-07-26 12:57 ` Anup Patel
2020-07-26 12:58 ` Anup Patel
2020-08-28 4:57 ` [RFC 0/2] Add risc-v vhost-net support Anup Patel
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=20200724085441.1514-2-jiangyifei@huawei.com \
--to=jiangyifei@huawei.com \
--cc=anup.patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=dengkai1@huawei.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=limingwang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.com \
--cc=victor.zhangxiaofeng@huawei.com \
--cc=wu.wubin@huawei.com \
--cc=zhang.zhanghailiang@huawei.com \
/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).