From: Andrew Jones <ajones@ventanamicro•com>
To: linux-riscv@lists•infradead.org, linux-next@vger•kernel.org,
linux-kernel@vger•kernel.org, kvm@vger•kernel.org,
kvm-riscv@lists•infradead.org
Cc: paul.walmsley@sifive•com, palmer@dabbelt•com,
aou@eecs•berkeley.edu, anup@brainfault•org,
atishp@atishpatra•org, rdunlap@infradead•org,
sfr@canb•auug.org.au, mpe@ellerman•id.au, npiggin@gmail•com,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH] RISC-V: KVM: Require HAVE_KVM
Date: Thu, 4 Jan 2024 11:52:07 +0100 [thread overview]
Message-ID: <20240104-d5ebb072b91a6f7abbb2ac76@orel> (raw)
In-Reply-To: <20240104104307.16019-2-ajones@ventanamicro.com>
This applies to linux-next, but I forgot to append -next to the PATCH
prefix.
On Thu, Jan 04, 2024 at 11:43:08AM +0100, Andrew Jones wrote:
> KVM requires EVENTFD, which is selected by HAVE_KVM. Other KVM
> supporting architectures select HAVE_KVM and then their KVM
> Kconfigs ensure its there with a depends on HAVE_KVM. Make RISCV
> consistent with that approach which fixes configs which have KVM
> but not EVENTFD, as was discovered with a randconfig test.
>
> Reported-by: Randy Dunlap <rdunlap@infradead•org>
> Closes: https://lore.kernel.org/all/44907c6b-c5bd-4e4a-a921-e4d3825539d8@infradead.org/
I think powerpc may need a patch like this as well, since I don't see
anything ensuring EVENTFD is selected for it anymore either.
Thanks,
drew
> Signed-off-by: Andrew Jones <ajones@ventanamicro•com>
> ---
> arch/riscv/Kconfig | 1 +
> arch/riscv/kvm/Kconfig | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index a935a5f736b9..daba06a3b76f 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -128,6 +128,7 @@ config RISCV
> select HAVE_KPROBES if !XIP_KERNEL
> select HAVE_KPROBES_ON_FTRACE if !XIP_KERNEL
> select HAVE_KRETPROBES if !XIP_KERNEL
> + select HAVE_KVM
> # https://github.com/ClangBuiltLinux/linux/issues/1881
> select HAVE_LD_DEAD_CODE_DATA_ELIMINATION if !LD_IS_LLD
> select HAVE_MOVE_PMD
> diff --git a/arch/riscv/kvm/Kconfig b/arch/riscv/kvm/Kconfig
> index 1fd76aee3b71..36fa8ec9e5ba 100644
> --- a/arch/riscv/kvm/Kconfig
> +++ b/arch/riscv/kvm/Kconfig
> @@ -19,7 +19,7 @@ if VIRTUALIZATION
>
> config KVM
> tristate "Kernel-based Virtual Machine (KVM) support (EXPERIMENTAL)"
> - depends on RISCV_SBI && MMU
> + depends on HAVE_KVM && RISCV_SBI && MMU
> select HAVE_KVM_IRQCHIP
> select HAVE_KVM_IRQ_ROUTING
> select HAVE_KVM_MSI
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-01-04 10:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 10:43 [PATCH] RISC-V: KVM: Require HAVE_KVM Andrew Jones
2024-01-04 10:52 ` Andrew Jones [this message]
2024-01-04 11:07 ` Alexandre Ghiti
2024-01-04 11:21 ` Andrew Jones
2024-01-04 11:33 ` 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=20240104-d5ebb072b91a6f7abbb2ac76@orel \
--to=ajones@ventanamicro$(echo .)com \
--cc=anup@brainfault$(echo .)org \
--cc=aou@eecs$(echo .)berkeley.edu \
--cc=atishp@atishpatra$(echo .)org \
--cc=kvm-riscv@lists$(echo .)infradead.org \
--cc=kvm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-riscv@lists$(echo .)infradead.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=npiggin@gmail$(echo .)com \
--cc=palmer@dabbelt$(echo .)com \
--cc=paul.walmsley@sifive$(echo .)com \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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