From: Harald Freudenberger <freude@linux.ibm.com>
To: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Cc: richard.henderson@linaro.org, iii@linux.ibm.com,
david@kernel.org, thuth@redhat.com, berrange@redhat.com,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
linux390-list@tuxmaker.boeblingen.de.ibm.com,
linux-s390@vger.kernel.org, dengler@linux.ibm.com,
borntraeger@linux.ibm.com, fcallies@linux.ibm.com,
cohuck@redhat.com
Subject: Re: [PATCH v8 01/18] target/s390x: Fix wrong address handling in address loops
Date: Mon, 29 Jun 2026 14:43:39 +0200 [thread overview]
Message-ID: <ddf3dc604cdc0e2d8294166306cb2187@linux.ibm.com> (raw)
In-Reply-To: <e217579b-50be-431d-8703-a19b3058f90b@oss.qualcomm.com>
On 2026-06-25 12:37, Philippe Mathieu-Daudé wrote:
> On 25/6/26 09:31, Harald Freudenberger wrote:
>> On 2026-06-24 12:05, Philippe Mathieu-Daudé wrote:
>>> Hi Harald,
>>>
>>> On 24/6/26 10:09, Harald Freudenberger wrote:
>>>> With the introduction of the address wrapping function
>>>> wrap_address() the result can't be used to walk the
>>>> source address any more. So introduce a new local variable
>>>> to hold the wrapped address to avoid mixing source and
>>>> wrapped address value.
>>>>
>>>> Fixes: fcc2699d41 ("target/s390x: Have MSA helper pass a mmu_idx
>>>> argument")
>>>
>>> This commit merely added an argument. I suppose you meant
>>> 9f17bfdab42 ("target/s390x: support SHA-512 extensions").
>>>
>>
>> No. Commit fcc2699d41 ("target/s390x: Have MSA helper pass a mmu_idx
>> argument")
>> introduces the mmu_idx with the wrap_address() function or macro.
>
> You are saying the same, not really explaining, I'm not following...
>
I rephrased my wording regarding this fix. Please see v9 coming soon.
>> And the result was something like this:
>>
>> for (int i = 0; i < 8; i++, addr += 8) {
>> addr = wrap_address(env, addr);
>> a[i] = cpu_ldq_mmu(env, addr, oi, ra);
>> }
>>
>> This code reuses the addr variable in the loop
>> by setting addr to the wrapped address but after
>> that the loop adds +8 to this wrapped address.
>> This code only works as long as the wrapped address
>> is equal to the address put put in.
>> Thus introduce another intermediate variable which
>> holds the wrapped address:
>>
>> for (int i = 0; i < 8; i++, addr += 8) {
>> uint64_t _addr = wrap_address(env, addr);
>> a[i] = cpu_ldq_mmu(env, _addr, oi, ra);
>> }
>>
>> Of course it would also work with a direct replacement:
>>
>> for (int i = 0; i < 8; i++, addr += 8) {
>> a[i] = cpu_ldq_mmu(env, wrap_address(env, addr), oi, ra);
>> }
>>
>> but this isn't that readable.
>>
>>>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>>>> ---
>>>> target/s390x/tcg/crypto_helper.c | 16 ++++++++--------
>>>> 1 file changed, 8 insertions(+), 8 deletions(-)
>>>>
>>>> diff --git a/target/s390x/tcg/crypto_helper.c b/target/s390x/tcg/
>>>> crypto_helper.c
>>>> index ae392bce0e..29ad2aff43 100644
>>>> --- a/target/s390x/tcg/crypto_helper.c
>>>> +++ b/target/s390x/tcg/crypto_helper.c
>>>> @@ -126,8 +126,8 @@ static void sha512_read_icv(CPUS390XState *env,
>>>> const int mmu_idx,
>>>> const MemOpIdx oi = make_memop_idx(MO_BE | MO_64 | MO_UNALN,
>>>> mmu_idx);
>>>> for (int i = 0; i < 8; i++, addr += 8) {
>>>> - addr = wrap_address(env, addr);
>>>> - a[i] = cpu_ldq_mmu(env, addr, oi, ra);
>>>> + uint64_t _addr = wrap_address(env, addr);
>>>
>>> s/_addr/wa/ or even directly inline?
>>>
>>> a[i] = cpu_ldq_mmu(env, wrap_address(env, addr), oi, ra);
>>>
>>>> + a[i] = cpu_ldq_mmu(env, _addr, oi, ra);
>>>> }
>>>> }
>>
next prev parent reply other threads:[~2026-06-29 12:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 8:09 [PATCH v8 00/18] target/s390x: Extend qemu CPACF support Harald Freudenberger
2026-06-24 8:09 ` [PATCH v8 01/18] target/s390x: Fix wrong address handling in address loops Harald Freudenberger
2026-06-24 10:05 ` Philippe Mathieu-Daudé
2026-06-25 7:31 ` Harald Freudenberger
2026-06-25 10:37 ` Philippe Mathieu-Daudé
2026-06-29 12:43 ` Harald Freudenberger [this message]
2026-06-29 12:26 ` Harald Freudenberger
2026-06-24 12:56 ` Ilya Leoshkevich
2026-06-29 12:57 ` Harald Freudenberger
2026-06-30 9:33 ` Ilya Leoshkevich
2026-06-30 10:23 ` Harald Freudenberger
2026-06-30 10:54 ` Ilya Leoshkevich
2026-06-30 14:19 ` Philippe Mathieu-Daudé
2026-07-01 7:42 ` Harald Freudenberger
2026-07-01 8:52 ` Ilya Leoshkevich
2026-06-24 8:09 ` [PATCH v8 02/18] target/s390x: Rework s390 cpacf implementations Harald Freudenberger
2026-06-24 14:27 ` Ilya Leoshkevich
2026-06-24 8:10 ` [PATCH v8 03/18] target/s390x: Move cpacf sha512 code into a new file Harald Freudenberger
2026-06-24 10:07 ` Philippe Mathieu-Daudé
2026-06-24 14:30 ` Ilya Leoshkevich
2026-06-24 8:10 ` [PATCH v8 04/18] target/s390x: Support cpacf sha256 Harald Freudenberger
2026-06-24 14:39 ` Ilya Leoshkevich
2026-06-24 8:10 ` [PATCH v8 05/18] target/s390x: Support AES ECB for cpacf km instruction Harald Freudenberger
2026-06-24 17:13 ` Ilya Leoshkevich
2026-06-24 8:10 ` [PATCH v8 06/18] target/s390x: Support AES CBC for cpacf kmc instruction Harald Freudenberger
2026-06-24 17:22 ` Ilya Leoshkevich
2026-06-30 13:59 ` Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 07/18] target/s390x: Support AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-06-24 17:26 ` Ilya Leoshkevich
2026-06-25 7:17 ` Harald Freudenberger
2026-06-30 13:58 ` Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 08/18] target/s390x: Minimal AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 09/18] target/s390x: Support AES XTS for cpacf km instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 10/18] target/s390x: Support pckmo encrypt AES subfunctions Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 11/18] target/s390x: Support protected key AES ECB for cpacf km instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 12/18] target/s390x: Support protected key AES CBC for cpacf kmc instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 13/18] target/s390x: Support protected key AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 14/18] target/s390x: Minimal protected key AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 15/18] target/s390x: Support protected key AES XTS for cpacf km instruction Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 16/18] docs/s390: Document CPACF instructions support Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 17/18] crypto: Add aes-helpers file to support some AES modes Harald Freudenberger
2026-06-24 8:10 ` [PATCH v8 18/18] target/s390x: Use generic AES helper functions Harald Freudenberger
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=ddf3dc604cdc0e2d8294166306cb2187@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux390-list@tuxmaker.boeblingen.de.ibm.com \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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