From: Marc Zyngier <maz@kernel.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: anshuman.khandual@arm.com, linux-arm-kernel@lists.infradead.org,
Christoffer Dall <christoffer.dall@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
stable@vger.kernel.org, Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH] kvm: arm64: nvhe: Save the SPE context early
Date: Tue, 2 Mar 2021 18:57:11 +0000 [thread overview]
Message-ID: <161471117620.3770794.12358302238773672698.b4-ty@kernel.org> (raw)
In-Reply-To: <20210302120345.3102874-1-suzuki.poulose@arm.com>
On Tue, 2 Mar 2021 12:03:45 +0000, Suzuki K Poulose wrote:
> The nVHE KVM hyp drains and disables the SPE buffer, before
> entering the guest, as the EL1&0 translation regime
> is going to be loaded with that of the guest.
>
> But this operation is performed way too late, because :
> - The owning translation regime of the SPE buffer
> is transferred to EL2. (MDCR_EL2_E2PB == 0)
> - The guest Stage1 is loaded.
>
> [...]
Applied to kvmarm-master/fixes, thanks!
[1/1] kvm: arm64: nvhe: Save the SPE context early
commit: cfe1e2b6949785e90e84918295f2be1b6fd152b6
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2021-03-03 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-02 12:03 [PATCH] kvm: arm64: nvhe: Save the SPE context early Suzuki K Poulose
2021-03-02 18:57 ` Marc Zyngier [this message]
2021-03-15 8:49 FAILED: patch "[PATCH] KVM: arm64: nvhe: Save the SPE context early" failed to apply to 4.19-stable tree gregkh
2021-03-17 11:50 ` [PATCH] KVM: arm64: nvhe: Save the SPE context early Suzuki K Poulose
2021-03-17 13:58 ` Marc Zyngier
2021-03-15 8:49 FAILED: patch "[PATCH] KVM: arm64: nvhe: Save the SPE context early" failed to apply to 5.4-stable tree gregkh
2021-03-16 18:33 ` [PATCH] KVM: arm64: nvhe: Save the SPE context early Suzuki K Poulose
2021-03-17 13:59 ` Marc Zyngier
2021-03-18 13:07 ` Sasha Levin
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=161471117620.3770794.12358302238773672698.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.org \
--cc=suzuki.poulose@arm.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).