From: Marc Zyngier <maz@kernel.org>
To: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Cc: Peng Liang <liangpeng10@huawei.com>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kernel-team@android.com
Subject: [PATCH v2 0/3] KVM: arm64: Another set of CSV2-related fixes
Date: Tue, 10 Nov 2020 14:13:05 +0000 [thread overview]
Message-ID: <20201110141308.451654-1-maz@kernel.org> (raw)
This small series addresses a couple of Spectre-v2 related issues:
- Fix a live migration regression introduced with the setting of CSV2
on systems that are not affected by Spectre-v2, but that don't
directly expose it in ID_AA64PFR0_EL1
- Inject an UNDEF exception if the guest tries to access any of
SCXTNUM_ELx, as we don't advertise it to guests.
Patches on top of 5.10-rc2.
* From v1:
- Only register a new value for CSV2 on a valid write to ID_AA64PFR0_EL1
- Delete even more code in patch #2
Marc Zyngier (3):
KVM: arm64: Allow setting of ID_AA64PFR0_EL1.CSV2 from userspace
KVM: arm64: Unify trap handlers injecting an UNDEF
KVM: arm64: Handle SCXTNUM_ELx traps
arch/arm64/include/asm/kvm_host.h | 2 +
arch/arm64/include/asm/sysreg.h | 4 ++
arch/arm64/kvm/arm.c | 16 +++++
arch/arm64/kvm/sys_regs.c | 111 ++++++++++++++++++------------
4 files changed, 89 insertions(+), 44 deletions(-)
--
2.28.0
next reply other threads:[~2020-11-10 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:13 Marc Zyngier [this message]
2020-11-10 14:13 ` [PATCH v2 1/3] KVM: arm64: Allow setting of ID_AA64PFR0_EL1.CSV2 from userspace Marc Zyngier
2020-11-11 22:01 ` Will Deacon
2020-11-10 14:13 ` [PATCH v2 2/3] KVM: arm64: Unify trap handlers injecting an UNDEF Marc Zyngier
2020-11-11 22:01 ` Will Deacon
2020-11-10 14:13 ` [PATCH v2 3/3] KVM: arm64: Handle SCXTNUM_ELx traps 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=20201110141308.451654-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=liangpeng10@huawei.com \
--cc=linux-arm-kernel@lists.infradead.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).