From: Marc Zyngier <maz@kernel.org>
To: Mostafa Saleh <smostafa@google.com>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, corbet@lwn.net,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] Documentation: Update the behaviour of "kvm-arm.mode"
Date: Thu, 24 Oct 2024 10:39:45 +0100 [thread overview]
Message-ID: <86v7xh3km6.wl-maz@kernel.org> (raw)
In-Reply-To: <20241023171244.4031151-1-smostafa@google.com>
Hi Mostafa,
On Wed, 23 Oct 2024 18:12:43 +0100,
Mostafa Saleh <smostafa@google.com> wrote:
>
> Commit 5053c3f0519c ("KVM: arm64: Use hVHE in pKVM by default on CPUs with
> VHE support") modified the behaviour of "kvm-arm.mode=protected" without
> the updating the kernel parameters doc.
>
> Update it to match the current implementation.
>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
>
> Signed-off-by: Mostafa Saleh <smostafa@google.com>
> ---
> Documentation/admin-guide/kernel-parameters.txt | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index bb48ae24ae69..59a0dd7e2de6 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -2723,8 +2723,12 @@
> nvhe: Standard nVHE-based mode, without support for
> protected guests.
>
> - protected: nVHE-based mode with support for guests whose
> + protected: hVHE-based mode with support for guests whose
> state is kept private from the host.
> + In case hVHE is not supported in hardware, it will
nit: it is VHE that is supported or not, hVHE is only a SW concept.
> + boot with protected nVHE.
> + nVHE protected mode can still be forced on VHE systems
> + using "kvm_arm.mode=protected arm64_sw.hvhe=0 id_aa64mmfr1.vh=0"
This opens another question: none of the arm_sw.*, nor any of the
id_aa64* parameters are described (basically, anything that's in
arch/arm64/kernel/pi/id_override.c). What should we do about these?
>
> nested: VHE-based mode with support for nested
> virtualization. Requires at least ARMv8.3
Huh, another nit to fix. We only support nested with ARMv8.4 (with
FEAT_NV2), as the ARMv8.3 version (the original FEAT_NV) is too ugly
for words.
Mind addressing this?
Thanks!
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-10-24 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 17:12 [PATCH] Documentation: Update the behaviour of "kvm-arm.mode" Mostafa Saleh
2024-10-24 9:39 ` Marc Zyngier [this message]
2024-10-24 11:32 ` Mostafa Saleh
2024-10-24 11:46 ` 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=86v7xh3km6.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smostafa@google.com \
--cc=will@kernel.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).