From: Mark Brown <broonie@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anup Patel <anup@brainfault.org>,
Atish Patra <atish.patra@linux.dev>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Jiakai Xu <xujiakai2025@iscas.ac.cn>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Andrew Jones <andrew.jones@oss.qualcomm.com>,
Shuah Khan <shuah@kernel.org>, Jiakai Xu <jiakaiPeanut@gmail.com>,
kvm-riscv@lists.infradead.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] KVM: arm64: Add memslot for ST_GPA_BASE in check_steal_time_uapi()
Date: Tue, 12 May 2026 19:39:56 +0900 [thread overview]
Message-ID: <agMDfLbkYrqzsTXs@sirena.co.uk> (raw)
In-Reply-To: <fb12c011-27d5-09e2-14fb-ec1728bb6c81@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
On Tue, May 12, 2026 at 10:49:23AM +0800, Zenghui Yu wrote:
> On 2026/5/12 9:59, Mark Brown wrote:
> > The regression in Linus' tree that is fixed by this patch is still
> > present today. Adding Marc and Oliver since this bug manifests on
> > arm64, adding Anup and Atish since the patch introducing the regression
> > was merged via RISC-V.
> Does fc240715fc50 [1] fix the selftest regression? It has been included
> in the latest KVM/arm64 pull request [2].
Ah, yes - that looks like it should also do the trick. Thanks for
making me aware of it!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-05-12 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260501021639.2563219-1-xujiakai2025@iscas.ac.cn>
2026-05-07 1:35 ` [PATCH] KVM: arm64: Add memslot for ST_GPA_BASE in check_steal_time_uapi() Mark Brown
2026-05-12 1:59 ` Mark Brown
2026-05-12 2:49 ` Zenghui Yu
2026-05-12 10:39 ` Mark Brown [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=agMDfLbkYrqzsTXs@sirena.co.uk \
--to=broonie@kernel.org \
--cc=andrew.jones@oss.qualcomm.com \
--cc=anup@brainfault.org \
--cc=atish.patra@linux.dev \
--cc=jiakaiPeanut@gmail.com \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xujiakai2025@iscas.ac.cn \
--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