All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
	kvmarm@lists.cs.columbia.edu, ascull@google.com,
	dbrazdil@google.com, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	kernel-team@android.com
Subject: Re: [PATCH] KVM: arm64: Allow KVM to be disabled from the command line
Date: Thu, 30 Sep 2021 11:29:49 +0100	[thread overview]
Message-ID: <87a6jutkyq.wl-maz@kernel.org> (raw)
In-Reply-To: <5bc623f2-e4c1-cc9c-683c-2f95648f1a68@arm.com>

On Wed, 29 Sep 2021 11:35:46 +0100,
Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> 
> On 03/09/2021 10:16, Marc Zyngier wrote:
> > Although KVM can be compiled out of the kernel, it cannot be disabled
> > at runtime. Allow this possibility by introducing a new mode that
> > will prevent KVM from initialising.
> > 
> > This is useful in the (limited) circumstances where you don't want
> > KVM to be available (what is wrong with you?), or when you want
> > to install another hypervisor instead (good luck with that).
> > 
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > ---
> >   Documentation/admin-guide/kernel-parameters.txt |  3 +++
> >   arch/arm64/include/asm/kvm_host.h               |  1 +
> >   arch/arm64/kernel/idreg-override.c              |  1 +
> >   arch/arm64/kvm/arm.c                            | 14 +++++++++++++-
> >   4 files changed, 18 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 91ba391f9b32..cc5f68846434 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -2365,6 +2365,9 @@
> >   	kvm-arm.mode=
> >   			[KVM,ARM] Select one of KVM/arm64's modes of operation.
> >   +			none: Forcefully disable KVM and run in nVHE
> > mode,
> > +			      preventing KVM from ever initialising.
> > +
> >   			nvhe: Standard nVHE-based mode, without support for
> >   			      protected guests.
> >   diff --git a/arch/arm64/include/asm/kvm_host.h
> > b/arch/arm64/include/asm/kvm_host.h
> > index f8be56d5342b..019490c67976 100644
> > --- a/arch/arm64/include/asm/kvm_host.h
> > +++ b/arch/arm64/include/asm/kvm_host.h
> > @@ -58,6 +58,7 @@
> >   enum kvm_mode {
> >   	KVM_MODE_DEFAULT,
> >   	KVM_MODE_PROTECTED,
> > +	KVM_MODE_NONE,
> >   };
> >   enum kvm_mode kvm_get_mode(void);
> >   diff --git a/arch/arm64/kernel/idreg-override.c
> > b/arch/arm64/kernel/idreg-override.c
> > index d8e606fe3c21..57013c1b6552 100644
> > --- a/arch/arm64/kernel/idreg-override.c
> > +++ b/arch/arm64/kernel/idreg-override.c
> > @@ -95,6 +95,7 @@ static const struct {
> >   	char	alias[FTR_ALIAS_NAME_LEN];
> >   	char	feature[FTR_ALIAS_OPTION_LEN];
> >   } aliases[] __initconst = {
> > +	{ "kvm-arm.mode=none",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=nvhe",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=protected",	"id_aa64mmfr1.vh=0" },
> >   	{ "arm64.nobti",		"id_aa64pfr1.bt=0" },
> > diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> > index fe102cd2e518..cdc70e238316 100644
> > --- a/arch/arm64/kvm/arm.c
> > +++ b/arch/arm64/kvm/arm.c
> > @@ -2064,6 +2064,11 @@ int kvm_arch_init(void *opaque)
> >   		return -ENODEV;
> >   	}
> >   +	if (kvm_get_mode() == KVM_MODE_NONE) {
> > +		kvm_info("KVM disabled from command line\n");
> > +		return -ENODEV;
> > +	}
> > +
> >   	in_hyp_mode = is_kernel_in_hyp_mode();
> >     	if (cpus_have_final_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE)
> > ||
> > @@ -2137,8 +2142,15 @@ static int __init early_kvm_mode_cfg(char *arg)
> >   		return 0;
> >   	}
> >   -	if (strcmp(arg, "nvhe") == 0 &&
> > !WARN_ON(is_kernel_in_hyp_mode()))
> > +	if (strcmp(arg, "nvhe") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> > +		kvm_mode = KVM_MODE_DEFAULT;
> >   		return 0;
> > +	}
> > +
> > +	if (strcmp(arg, "none") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> 
> nit: Does this really need to WARN here ? Unlike the "nvhe" case, if the
> user wants to keep the KVM out of the picture for, say debugging
> something, it is perfectly Ok to allow the kernel to be running at EL2
> without having to change the Firmware to alter the landing EL for the
> kernel ?

Well, the doc says "run in nVHE mode" and the option forces
id_aa64mmfr1.vh=0. The WARN_ON() will only fires on broken^Wfruity HW
that is VHE only. Note that this doesn't rely on any firmware change
(we drop from EL2 to EL1 and stay there).

We could add another option (none-vhe?) that stays at EL2 and still
disables KVM if there is an appetite for it.

> Otherwise,
> 
> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> 

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: kvm@vger.kernel.org, kernel-team@android.com,
	kvmarm@lists.cs.columbia.edu,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM: arm64: Allow KVM to be disabled from the command line
Date: Thu, 30 Sep 2021 11:29:49 +0100	[thread overview]
Message-ID: <87a6jutkyq.wl-maz@kernel.org> (raw)
In-Reply-To: <5bc623f2-e4c1-cc9c-683c-2f95648f1a68@arm.com>

On Wed, 29 Sep 2021 11:35:46 +0100,
Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> 
> On 03/09/2021 10:16, Marc Zyngier wrote:
> > Although KVM can be compiled out of the kernel, it cannot be disabled
> > at runtime. Allow this possibility by introducing a new mode that
> > will prevent KVM from initialising.
> > 
> > This is useful in the (limited) circumstances where you don't want
> > KVM to be available (what is wrong with you?), or when you want
> > to install another hypervisor instead (good luck with that).
> > 
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > ---
> >   Documentation/admin-guide/kernel-parameters.txt |  3 +++
> >   arch/arm64/include/asm/kvm_host.h               |  1 +
> >   arch/arm64/kernel/idreg-override.c              |  1 +
> >   arch/arm64/kvm/arm.c                            | 14 +++++++++++++-
> >   4 files changed, 18 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 91ba391f9b32..cc5f68846434 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -2365,6 +2365,9 @@
> >   	kvm-arm.mode=
> >   			[KVM,ARM] Select one of KVM/arm64's modes of operation.
> >   +			none: Forcefully disable KVM and run in nVHE
> > mode,
> > +			      preventing KVM from ever initialising.
> > +
> >   			nvhe: Standard nVHE-based mode, without support for
> >   			      protected guests.
> >   diff --git a/arch/arm64/include/asm/kvm_host.h
> > b/arch/arm64/include/asm/kvm_host.h
> > index f8be56d5342b..019490c67976 100644
> > --- a/arch/arm64/include/asm/kvm_host.h
> > +++ b/arch/arm64/include/asm/kvm_host.h
> > @@ -58,6 +58,7 @@
> >   enum kvm_mode {
> >   	KVM_MODE_DEFAULT,
> >   	KVM_MODE_PROTECTED,
> > +	KVM_MODE_NONE,
> >   };
> >   enum kvm_mode kvm_get_mode(void);
> >   diff --git a/arch/arm64/kernel/idreg-override.c
> > b/arch/arm64/kernel/idreg-override.c
> > index d8e606fe3c21..57013c1b6552 100644
> > --- a/arch/arm64/kernel/idreg-override.c
> > +++ b/arch/arm64/kernel/idreg-override.c
> > @@ -95,6 +95,7 @@ static const struct {
> >   	char	alias[FTR_ALIAS_NAME_LEN];
> >   	char	feature[FTR_ALIAS_OPTION_LEN];
> >   } aliases[] __initconst = {
> > +	{ "kvm-arm.mode=none",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=nvhe",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=protected",	"id_aa64mmfr1.vh=0" },
> >   	{ "arm64.nobti",		"id_aa64pfr1.bt=0" },
> > diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> > index fe102cd2e518..cdc70e238316 100644
> > --- a/arch/arm64/kvm/arm.c
> > +++ b/arch/arm64/kvm/arm.c
> > @@ -2064,6 +2064,11 @@ int kvm_arch_init(void *opaque)
> >   		return -ENODEV;
> >   	}
> >   +	if (kvm_get_mode() == KVM_MODE_NONE) {
> > +		kvm_info("KVM disabled from command line\n");
> > +		return -ENODEV;
> > +	}
> > +
> >   	in_hyp_mode = is_kernel_in_hyp_mode();
> >     	if (cpus_have_final_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE)
> > ||
> > @@ -2137,8 +2142,15 @@ static int __init early_kvm_mode_cfg(char *arg)
> >   		return 0;
> >   	}
> >   -	if (strcmp(arg, "nvhe") == 0 &&
> > !WARN_ON(is_kernel_in_hyp_mode()))
> > +	if (strcmp(arg, "nvhe") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> > +		kvm_mode = KVM_MODE_DEFAULT;
> >   		return 0;
> > +	}
> > +
> > +	if (strcmp(arg, "none") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> 
> nit: Does this really need to WARN here ? Unlike the "nvhe" case, if the
> user wants to keep the KVM out of the picture for, say debugging
> something, it is perfectly Ok to allow the kernel to be running at EL2
> without having to change the Firmware to alter the landing EL for the
> kernel ?

Well, the doc says "run in nVHE mode" and the option forces
id_aa64mmfr1.vh=0. The WARN_ON() will only fires on broken^Wfruity HW
that is VHE only. Note that this doesn't rely on any firmware change
(we drop from EL2 to EL1 and stay there).

We could add another option (none-vhe?) that stays at EL2 and still
disables KVM if there is an appetite for it.

> Otherwise,
> 
> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> 

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
	kvmarm@lists.cs.columbia.edu, ascull@google.com,
	dbrazdil@google.com, James Morse <james.morse@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	kernel-team@android.com
Subject: Re: [PATCH] KVM: arm64: Allow KVM to be disabled from the command line
Date: Thu, 30 Sep 2021 11:29:49 +0100	[thread overview]
Message-ID: <87a6jutkyq.wl-maz@kernel.org> (raw)
In-Reply-To: <5bc623f2-e4c1-cc9c-683c-2f95648f1a68@arm.com>

On Wed, 29 Sep 2021 11:35:46 +0100,
Suzuki K Poulose <suzuki.poulose@arm.com> wrote:
> 
> On 03/09/2021 10:16, Marc Zyngier wrote:
> > Although KVM can be compiled out of the kernel, it cannot be disabled
> > at runtime. Allow this possibility by introducing a new mode that
> > will prevent KVM from initialising.
> > 
> > This is useful in the (limited) circumstances where you don't want
> > KVM to be available (what is wrong with you?), or when you want
> > to install another hypervisor instead (good luck with that).
> > 
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > ---
> >   Documentation/admin-guide/kernel-parameters.txt |  3 +++
> >   arch/arm64/include/asm/kvm_host.h               |  1 +
> >   arch/arm64/kernel/idreg-override.c              |  1 +
> >   arch/arm64/kvm/arm.c                            | 14 +++++++++++++-
> >   4 files changed, 18 insertions(+), 1 deletion(-)
> > 
> > diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> > index 91ba391f9b32..cc5f68846434 100644
> > --- a/Documentation/admin-guide/kernel-parameters.txt
> > +++ b/Documentation/admin-guide/kernel-parameters.txt
> > @@ -2365,6 +2365,9 @@
> >   	kvm-arm.mode=
> >   			[KVM,ARM] Select one of KVM/arm64's modes of operation.
> >   +			none: Forcefully disable KVM and run in nVHE
> > mode,
> > +			      preventing KVM from ever initialising.
> > +
> >   			nvhe: Standard nVHE-based mode, without support for
> >   			      protected guests.
> >   diff --git a/arch/arm64/include/asm/kvm_host.h
> > b/arch/arm64/include/asm/kvm_host.h
> > index f8be56d5342b..019490c67976 100644
> > --- a/arch/arm64/include/asm/kvm_host.h
> > +++ b/arch/arm64/include/asm/kvm_host.h
> > @@ -58,6 +58,7 @@
> >   enum kvm_mode {
> >   	KVM_MODE_DEFAULT,
> >   	KVM_MODE_PROTECTED,
> > +	KVM_MODE_NONE,
> >   };
> >   enum kvm_mode kvm_get_mode(void);
> >   diff --git a/arch/arm64/kernel/idreg-override.c
> > b/arch/arm64/kernel/idreg-override.c
> > index d8e606fe3c21..57013c1b6552 100644
> > --- a/arch/arm64/kernel/idreg-override.c
> > +++ b/arch/arm64/kernel/idreg-override.c
> > @@ -95,6 +95,7 @@ static const struct {
> >   	char	alias[FTR_ALIAS_NAME_LEN];
> >   	char	feature[FTR_ALIAS_OPTION_LEN];
> >   } aliases[] __initconst = {
> > +	{ "kvm-arm.mode=none",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=nvhe",		"id_aa64mmfr1.vh=0" },
> >   	{ "kvm-arm.mode=protected",	"id_aa64mmfr1.vh=0" },
> >   	{ "arm64.nobti",		"id_aa64pfr1.bt=0" },
> > diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> > index fe102cd2e518..cdc70e238316 100644
> > --- a/arch/arm64/kvm/arm.c
> > +++ b/arch/arm64/kvm/arm.c
> > @@ -2064,6 +2064,11 @@ int kvm_arch_init(void *opaque)
> >   		return -ENODEV;
> >   	}
> >   +	if (kvm_get_mode() == KVM_MODE_NONE) {
> > +		kvm_info("KVM disabled from command line\n");
> > +		return -ENODEV;
> > +	}
> > +
> >   	in_hyp_mode = is_kernel_in_hyp_mode();
> >     	if (cpus_have_final_cap(ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE)
> > ||
> > @@ -2137,8 +2142,15 @@ static int __init early_kvm_mode_cfg(char *arg)
> >   		return 0;
> >   	}
> >   -	if (strcmp(arg, "nvhe") == 0 &&
> > !WARN_ON(is_kernel_in_hyp_mode()))
> > +	if (strcmp(arg, "nvhe") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> > +		kvm_mode = KVM_MODE_DEFAULT;
> >   		return 0;
> > +	}
> > +
> > +	if (strcmp(arg, "none") == 0 && !WARN_ON(is_kernel_in_hyp_mode())) {
> 
> nit: Does this really need to WARN here ? Unlike the "nvhe" case, if the
> user wants to keep the KVM out of the picture for, say debugging
> something, it is perfectly Ok to allow the kernel to be running at EL2
> without having to change the Firmware to alter the landing EL for the
> kernel ?

Well, the doc says "run in nVHE mode" and the option forces
id_aa64mmfr1.vh=0. The WARN_ON() will only fires on broken^Wfruity HW
that is VHE only. Note that this doesn't rely on any firmware change
(we drop from EL2 to EL1 and stay there).

We could add another option (none-vhe?) that stays at EL2 and still
disables KVM if there is an appetite for it.

> Otherwise,
> 
> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
> 

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-09-30 10:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03  9:16 [PATCH] KVM: arm64: Allow KVM to be disabled from the command line Marc Zyngier
2021-09-03  9:16 ` Marc Zyngier
2021-09-03  9:16 ` Marc Zyngier
2021-09-28 14:58 ` David Brazdil
2021-09-28 14:58   ` David Brazdil
2021-09-28 14:58   ` David Brazdil
2021-09-30 10:22   ` Marc Zyngier
2021-09-30 10:22     ` Marc Zyngier
2021-09-30 10:22     ` Marc Zyngier
2021-09-29 10:28 ` Will Deacon
2021-09-29 10:28   ` Will Deacon
2021-09-29 10:28   ` Will Deacon
2021-09-29 10:35 ` Suzuki K Poulose
2021-09-29 10:35   ` Suzuki K Poulose
2021-09-29 10:35   ` Suzuki K Poulose
2021-09-30 10:29   ` Marc Zyngier [this message]
2021-09-30 10:29     ` Marc Zyngier
2021-09-30 10:29     ` Marc Zyngier
2021-10-01  9:27     ` Suzuki K Poulose
2021-10-01  9:27       ` Suzuki K Poulose
2021-10-01  9:27       ` Suzuki K Poulose
2021-10-01 14:54       ` Marc Zyngier
2021-10-01 14:54         ` Marc Zyngier
2021-10-01 14:54         ` Marc Zyngier

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=87a6jutkyq.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=alexandru.elisei@arm.com \
    --cc=ascull@google.com \
    --cc=dbrazdil@google.com \
    --cc=james.morse@arm.com \
    --cc=kernel-team@android.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=suzuki.poulose@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.