From: Andrew Jones <ajones@ventanamicro.com>
To: linux-riscv@lists.infradead.org, kvm-riscv@lists.infradead.org
Cc: 'Palmer Dabbelt ' <palmer@dabbelt.com>,
'Anup Patel ' <anup@brainfault.org>,
'Paul Walmsley ' <paul.walmsley@sifive.com>,
'Atish Patra ' <atishp@atishpatra.org>,
'Albert Ou ' <aou@eecs.berkeley.edu>
Subject: [PATCH 2/2] RISC-V: KVM: Require alternatives
Date: Wed, 22 Mar 2023 20:28:58 +0100 [thread overview]
Message-ID: <20230322192858.1189272-3-ajones@ventanamicro.com> (raw)
In-Reply-To: <20230322192858.1189272-1-ajones@ventanamicro.com>
KVM makes use of riscv_has_extension_unlikely() to check for the
svinval extension. riscv_has_extension_unlikely() is built on
alternatives, which means KVM should ensure alternatives support
is available. Select RISCV_ALTERNATIVE from KVM.
Fixes: e8ad17d2b5f3 ("riscv: KVM: Switch has_svinval() to riscv_has_extension_unlikely()")
Signed-off-by: Andrew Jones <ajones@ventanamicro.com>
---
arch/riscv/kvm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/kvm/Kconfig b/arch/riscv/kvm/Kconfig
index 5bcb2d519b95..9dd61db0acc5 100644
--- a/arch/riscv/kvm/Kconfig
+++ b/arch/riscv/kvm/Kconfig
@@ -28,6 +28,7 @@ config KVM
select KVM_XFER_TO_GUEST_WORK
select MMU_NOTIFIER
select PREEMPT_NOTIFIERS
+ select RISCV_ALTERNATIVE
select SRCU
help
Support hosting virtualized guest machines.
--
2.39.2
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-03-22 19:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 19:28 [PATCH 0/2] RISC-V: KVM: Require alternatives Andrew Jones
2023-03-22 19:28 ` [PATCH 1/2] RISC-V: KVM: Alphabetize selects Andrew Jones
2023-04-07 11:47 ` Anup Patel
2023-03-22 19:28 ` Andrew Jones [this message]
2023-03-22 19:40 ` [PATCH 0/2] RISC-V: KVM: Require alternatives Conor Dooley
2023-03-23 17:57 ` Conor Dooley
2023-03-23 19:05 ` Andrew Jones
2023-03-24 11:32 ` Andrew Jones
2023-03-24 11:52 ` Conor Dooley
2023-03-24 11:56 ` Andrew Jones
2023-03-24 12:21 ` 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=20230322192858.1189272-3-ajones@ventanamicro.com \
--to=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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