From: Vincent Donnefort <vdonnefort@google.com>
To: Marc Zyngier <maz@kernel.org>, stable@vger.kernel.org, gregkh@kernel.org
Cc: kernel-team@android.com
Subject: Re: [PATCH] KVM: arm64: pkvm: Fixup boot mode to reflect that the kernel resumes from EL1
Date: Mon, 28 Nov 2022 16:21:28 +0000 [thread overview]
Message-ID: <Y4TgCOFgjMWuTTWe@google.com> (raw)
In-Reply-To: <20221108100138.3887862-1-vdonnefort@google.com>
On Tue, Nov 08, 2022 at 10:01:38AM +0000, Vincent Donnefort wrote:
> From: Marc Zyngier <maz@kernel.org>
>
> The kernel has an awfully complicated boot sequence in order to cope
> with the various EL2 configurations, including those that "enhanced"
> the architecture. We go from EL2 to EL1, then back to EL2, staying
> at EL2 if VHE capable and otherwise go back to EL1.
>
> Here's a paracetamol tablet for you.
>
> The cpu_resume path follows the same logic, because coming up with
> two versions of a square wheel is hard.
>
> However, things aren't this straightforward with pKVM, as the host
> resume path is always proxied by the hypervisor, which means that
> the kernel is always entered at EL1. Which contradicts what the
> __boot_cpu_mode[] array contains (it obviously says EL2).
>
> This thus triggers a HVC call from EL1 to EL2 in a vain attempt
> to upgrade from EL1 to EL2 VHE, which we are, funnily enough,
> reluctant to grant to the host kernel. This is also completely
> unexpected, and puzzles your average EL2 hacker.
>
> Address it by fixing up the boot mode at the point the host gets
> deprivileged. is_hyp_mode_available() and co already have a static
> branch to deal with this, making it pretty safe.
>
> Cc: <stable@vger.kernel.org> # 5.15+
> Reported-by: Vincent Donnefort <vdonnefort@google.com>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Tested-by: Vincent Donnefort <vdonnefort@google.com>
>
> ---
>
> This patch doesn't have an upstream version. It's been fixed by the side
> effect of another upstream patch. see conversation [1]
>
> [1] https://lore.kernel.org/all/20221011165400.1241729-1-maz@kernel.org/
>
> diff --git a/arch/arm64/kvm/arm.c b/arch/arm64/kvm/arm.c
> index 4cb265e15361..3fe816c244ce 100644
> --- a/arch/arm64/kvm/arm.c
> +++ b/arch/arm64/kvm/arm.c
> @@ -2000,6 +2000,17 @@ static int pkvm_drop_host_privileges(void)
> * once the host stage 2 is installed.
> */
> static_branch_enable(&kvm_protected_mode_initialized);
> +
> + /*
> + * Fixup the boot mode so that we don't take spurious round
> + * trips via EL2 on cpu_resume. Flush to the PoC for a good
> + * measure, so that it can be observed by a CPU coming out of
> + * suspend with the MMU off.
> + */
> + __boot_cpu_mode[0] = __boot_cpu_mode[1] = BOOT_CPU_MODE_EL1;
> + dcache_clean_poc((unsigned long)__boot_cpu_mode,
> + (unsigned long)(__boot_cpu_mode + 2));
> +
> on_each_cpu(_kvm_host_prot_finalize, &ret, 1);
> return ret;
> }
> --
> 2.38.1.431.g37b22c650d-goog
>
Hi Greg,
Any chance to pick this fix for 5.15?
Thanks!
--
Vincent.
next prev parent reply other threads:[~2022-11-28 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 10:01 [PATCH] KVM: arm64: pkvm: Fixup boot mode to reflect that the kernel resumes from EL1 Vincent Donnefort
2022-11-28 16:21 ` Vincent Donnefort [this message]
2022-11-28 17:19 ` Greg KH
2022-11-28 17:24 ` Vincent Donnefort
2022-11-28 18:01 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2022-10-11 16:54 Marc Zyngier
2022-10-11 16:54 ` Marc Zyngier
2022-10-11 16:54 ` Marc Zyngier
2022-10-11 18:48 ` Oliver Upton
2022-10-11 18:48 ` Oliver Upton
2022-10-11 18:48 ` Oliver Upton
2022-10-11 20:58 ` Marc Zyngier
2022-10-11 20:58 ` Marc Zyngier
2022-10-11 20:58 ` Marc Zyngier
2022-10-13 13:33 ` Vincent Donnefort
2022-10-13 13:33 ` Vincent Donnefort
2022-10-13 13:33 ` Vincent Donnefort
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=Y4TgCOFgjMWuTTWe@google.com \
--to=vdonnefort@google.com \
--cc=gregkh@kernel.org \
--cc=kernel-team@android.com \
--cc=maz@kernel.org \
--cc=stable@vger.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 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.