From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH] KVM: arm64: Fix S1/S2 combination when FWB==1 and S2 has Device memory type
Date: Tue, 26 Nov 2024 07:59:26 -0800 [thread overview]
Message-ID: <173263668483.68510.4488046767973544400.b4-ty@linux.dev> (raw)
In-Reply-To: <20241125094756.609590-1-maz@kernel.org>
On Mon, 25 Nov 2024 09:47:56 +0000, Marc Zyngier wrote:
> The G.a revision of the ARM ARM had it pretty clear that HCR_EL2.FWB
> had no influence on "The way that stage 1 memory types and attributes
> are combined with stage 2 Device type and attributes." (D5.5.5).
>
> However, this wording was lost in further revisions of the architecture.
>
> Restore the intended behaviour, which is to take the strongest memory
> type of S1 and S2 in this case, as if FWB was 0. The specification is
> being fixed accordingly.
>
> [...]
Applied to fixes, thanks!
[1/1] KVM: arm64: Fix S1/S2 combination when FWB==1 and S2 has Device memory type
https://git.kernel.org/kvmarm/kvmarm/c/6fc3a49f2385
--
Best,
Oliver
prev parent reply other threads:[~2024-11-26 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 9:47 [PATCH] KVM: arm64: Fix S1/S2 combination when FWB==1 and S2 has Device memory type Marc Zyngier
2024-11-26 15:27 ` Oliver Upton
2024-11-26 16:30 ` Marc Zyngier
2024-11-26 18:48 ` Oliver Upton
2024-11-26 15:59 ` Oliver Upton [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=173263668483.68510.4488046767973544400.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=alexandru.elisei@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--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;
as well as URLs for NNTP newsgroup(s).