From: Cornelia Huck <cohuck@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Matthew Rosato" <mjrosato@linux.ibm.com>,
qemu-devel@nongnu.org
Cc: Pierrick Bouvier <pierrick.bouvier@linaro.org>,
Ilya Leoshkevich <iii@linux.ibm.com>,
Anton Johansson <anjo@rev.ng>, Eric Farman <farman@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
Halil Pasic <pasic@linux.ibm.com>,
qemu-s390x@nongnu.org, David Hildenbrand <david@kernel.org>
Subject: Re: [PATCH 0/5] target/s390x: Forbid to use legacy ldst_phys() API
Date: Tue, 14 Apr 2026 13:33:23 +0200 [thread overview]
Message-ID: <87tstdbwu4.fsf@redhat.com> (raw)
In-Reply-To: <640ddcc2-f373-4738-8e66-50effe56de4e@linaro.org>
On Tue, Apr 14 2026, Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
> On 21/3/26 16:26, Philippe Mathieu-Daudé wrote:
>> On 20/3/26 20:28, Matthew Rosato wrote:
>>> On 3/19/26 2:51 PM, Philippe Mathieu-Daudé wrote:
>>>> Replace legacy ld/st_phys() by address_space_ld/st()
>>>> then lock the target again further legacy API uses.
>>>>
>>>> Philippe Mathieu-Daudé (5):
>>>> target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (cpu)
>>>> target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (mmu)
>>>> target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (tcg)
>>>> target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (kvm)
>>>> configs/targets: Restrict the legacy ldst_phys() API on s390x target
>>>
>>> For the series:
>>>
>>> Reviewed-by: Matthew Rosato <mjrosato@linux.ibm.com>
>>>
>>> For good measure I also ran some s390x kvm regression tests, took a
>>> less comprehensive spin with a tcg s390x guest (on s390 host), and
>>> forced a few of these codepaths as a sanity check.
>
> Does that mean we can also add:
>
> Tested-by: Matthew Rosato <mjrosato@linux.ibm.com>
>
> ?
I was planning to pick this via s390-next, I can add T-b if desired.
next prev parent reply other threads:[~2026-04-14 11:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 18:51 [PATCH 0/5] target/s390x: Forbid to use legacy ldst_phys() API Philippe Mathieu-Daudé
2026-03-19 18:51 ` [PATCH 1/5] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (cpu) Philippe Mathieu-Daudé
2026-03-19 18:52 ` [PATCH 2/5] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (mmu) Philippe Mathieu-Daudé
2026-03-19 18:52 ` [PATCH 3/5] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (tcg) Philippe Mathieu-Daudé
2026-03-19 18:52 ` [PATCH 4/5] target/s390x: Replace legacy ld/st_phys -> address_space_ld/st (kvm) Philippe Mathieu-Daudé
2026-03-19 18:52 ` [PATCH 5/5] configs/targets: Restrict the legacy ldst_phys() API on s390x target Philippe Mathieu-Daudé
2026-03-20 19:28 ` [PATCH 0/5] target/s390x: Forbid to use legacy ldst_phys() API Matthew Rosato
2026-03-21 15:26 ` Philippe Mathieu-Daudé
2026-04-13 22:41 ` Philippe Mathieu-Daudé
2026-04-14 11:33 ` Cornelia Huck [this message]
2026-04-16 11:39 ` Philippe Mathieu-Daudé
2026-04-16 12:59 ` Matthew Rosato
2026-04-17 15:14 ` Cornelia Huck
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=87tstdbwu4.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=anjo@rev.ng \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.