From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oupton@kernel.org>, Fuad Tabba <fuad.tabba@linux.dev>
Cc: Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Christoffer Dall <christoffer.dall@linaro.org>,
Victor Kamensky <victor.kamensky@linaro.org>,
Fuad Tabba <tabba@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] KVM: arm64: Fix and test MMIO sign-extending loads
Date: Mon, 6 Jul 2026 17:19:46 +0100 [thread overview]
Message-ID: <178335476045.1423186.16967081834090661030.b4-ty@kernel.org> (raw)
In-Reply-To: <20260706115522.954913-1-fuad.tabba@linux.dev>
On Mon, 06 Jul 2026 12:55:20 +0100, Fuad Tabba wrote:
> Changes since v2 [1]:
> - Patch 2: dropped the second make_el0_accessible() call and the
> el0_be_loads_end symbol; the EL0 code page does not need its
> user-access bit set because it is fetched, not loaded. (sashiko)
>
> Oliver's Reviewed-by is on patch 1 only: the code there is unchanged
> since v1.
>
> [...]
Applied to fixes, thanks!
[1/2] KVM: arm64: Fix sign-extension of MMIO loads
commit: 85f56708a443ec02a290878f00d79a1ff5110e41
[2/2] KVM: arm64: selftests: Add MMIO sign-extending load test
commit: 65a38ddeaeed1a962bc1b4ca03c98201c877fea5
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-07-06 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 11:55 [PATCH v3 0/2] KVM: arm64: Fix and test MMIO sign-extending loads Fuad Tabba
2026-07-06 11:55 ` [PATCH v3 1/2] KVM: arm64: Fix sign-extension of MMIO loads Fuad Tabba
2026-07-06 11:55 ` [PATCH v3 2/2] KVM: arm64: selftests: Add MMIO sign-extending load test Fuad Tabba
2026-07-06 16:19 ` 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=178335476045.1423186.16967081834090661030.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=victor.kamensky@linaro.org \
--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