[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210317141714.383046-1-qperret@google.com>
Date: Wed, 17 Mar 2021 14:17:12 +0000
From: Quentin Perret <qperret@...gle.com>
To: qperret@...gle.com
Cc: catalin.marinas@....com, will@...nel.org, maz@...nel.org,
james.morse@....com, julien.thierry.kdev@...il.com,
suzuki.poulose@....com, android-kvm@...gle.com, seanjc@...gle.com,
linux-kernel@...r.kernel.org, robh+dt@...nel.org,
linux-arm-kernel@...ts.infradead.org, kernel-team@...roid.com,
kvmarm@...ts.cs.columbia.edu, tabba@...gle.com, ardb@...nel.org,
mark.rutland@....com, dbrazdil@...gle.com, mate.toth-pal@....com
Subject: [PATCH 0/2] Fixes for FWB
Hi folks,
This is an alternative solution to the KVM_PGTABLE_PROT_S2_NOFWB patch I
shared earlier (and which is a bit of a hack).
With this series we basically force FWB off for the host stage-2, even
when the CPUs support it. This is done by passing flags to the pgtable
init function, and propagating it down where needed. It's a bit more
intrusive, but cleaner conceptually.
Thoughts?
Thanks,
Quentin
Quentin Perret (2):
KVM: arm64: Introduce KVM_PGTABLE_S2_NOFWB Stage-2 flag
KVM: arm64: Disable FWB in host stage-2
arch/arm64/include/asm/kvm_pgtable.h | 19 +++++++++--
arch/arm64/include/asm/pgtable-prot.h | 4 +--
arch/arm64/kvm/hyp/nvhe/mem_protect.c | 6 ++--
arch/arm64/kvm/hyp/pgtable.c | 49 +++++++++++++++++----------
4 files changed, 52 insertions(+), 26 deletions(-)
--
2.31.0.rc2.261.g7f71774620-goog
Powered by blists - more mailing lists