[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173660773861.818546.3192188976167687860.b4-ty@kernel.org>
Date: Sat, 11 Jan 2025 15:02:33 +0000
From: Marc Zyngier <maz@...nel.org>
To: Oliver Upton <oliver.upton@...ux.dev>,
Joey Gouly <joey.gouly@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Zenghui Yu <yuzenghui@...wei.com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
"Rob Herring (Arm)" <robh@...nel.org>
Cc: Mark Rutland <mark.rutland@....com>,
Anshuman Khandual <anshuman.khandual@....com>,
linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: arm64: Explicitly handle BRBE traps as UNDEFINED
On Thu, 09 Jan 2025 16:38:36 -0600, Rob Herring (Arm) wrote:
> The Branch Record Buffer Extension (BRBE) adds a number of system
> registers and instructions which we don't currently intend to expose to
> guests. Our existing logic handles this safely, but this could be
> improved with some explicit handling of BRBE.
>
> KVM currently hides BRBE from guests: the cpufeature code's
> ftr_id_aa64dfr0[] table doesn't have an entry for the BRBE field, and so
> this will be zero in the sanitised value of ID_AA64DFR0 exposed to
> guests via read_sanitised_id_aa64dfr0_el1().
>
> [...]
Applied to next, thanks!
[1/1] KVM: arm64: Explicitly handle BRBE traps as UNDEFINED
commit: a7f1fa5564be565bd4bc18875bb46ffd0c01d292
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists