From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
"Rob Herring (Arm)" <robh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: Explicitly handle BRBE traps as UNDEFINED
Date: Sat, 11 Jan 2025 15:02:33 +0000 [thread overview]
Message-ID: <173660773861.818546.3192188976167687860.b4-ty@kernel.org> (raw)
In-Reply-To: <20250109223836.419240-1-robh@kernel.org>
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.
prev parent reply other threads:[~2025-01-11 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 22:38 Rob Herring (Arm)
2025-01-11 15:02 ` Marc Zyngier [this message]
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=173660773861.818546.3192188976167687860.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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
all inboxes | Powered by JetHome®