* [PATCH v2 1/1] s390/ap: Fix MAPML computation
@ 2026-08-05 9:29 Finn Callies
2026-08-05 9:45 ` sashiko-bot
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Finn Callies @ 2026-08-05 9:29 UTC (permalink / raw)
To: hca, gor, agordeev; +Cc: linux-s390, fcallies, freude
When the TAPQ subfunction of PQAP returns a value between 0 and 3 in the
ml field, the Principles of Operation states that the Maximum AP Message
Length (MAPML) must be 12 KB.
The previous code incorrectly calculated smaller sizes for ml values 1-2:
- ml=1: 4 KB instead of 12 KB
- ml=2: 8 KB instead of 12 KB
While no current hardware reports ml=1 or ml=2, this fix ensures correct
behavior for specification compliance and future-proofing.
The fix ensures all ml values 0-3 correctly use the 12 KB default, with
only values 4+ using the formula ml * 4096.
Reviewed-by: Harald Freudenberger <freude@linux.ibm.com>
Signed-off-by: Finn Callies <fcallies@linux.ibm.com>
---
drivers/s390/crypto/ap_card.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/s390/crypto/ap_card.c b/drivers/s390/crypto/ap_card.c
index e827fbeb76fb..c86397f4ddcd 100644
--- a/drivers/s390/crypto/ap_card.c
+++ b/drivers/s390/crypto/ap_card.c
@@ -241,7 +241,7 @@ struct ap_card *ap_card_create(int id, struct ap_tapq_hwinfo hwinfo,
ac->ap_dev.device_type = comp_type;
ac->hwinfo = hwinfo;
ac->id = id;
- ac->maxmsgsize = hwinfo.ml > 0 ?
+ ac->maxmsgsize = hwinfo.ml > 3 ?
hwinfo.ml * AP_TAPQ_ML_FIELD_CHUNK_SIZE : AP_DEFAULT_MAX_MSG_SIZE;
return ac;
--
Finn Callies <fcallies@linux.ibm.com>
Linux on Z - crypto
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH v2 1/1] s390/ap: Fix MAPML computation
2026-08-05 9:29 [PATCH v2 1/1] s390/ap: Fix MAPML computation Finn Callies
@ 2026-08-05 9:45 ` sashiko-bot
2026-08-05 9:57 ` Heiko Carstens
2026-08-05 13:01 ` Vasily Gorbik
2 siblings, 0 replies; 4+ messages in thread
From: sashiko-bot @ 2026-08-05 9:45 UTC (permalink / raw)
To: Finn Callies; +Cc: linux-s390, Vasily Gorbik, Heiko Carstens, Alexander Gordeev
> When the TAPQ subfunction of PQAP returns a value between 0 and 3 in the
> ml field, the Principles of Operation states that the Maximum AP Message
> Length (MAPML) must be 12 KB.
>
> The previous code incorrectly calculated smaller sizes for ml values 1-2:
> - ml=1: 4 KB instead of 12 KB
> - ml=2: 8 KB instead of 12 KB
>
> While no current hardware reports ml=1 or ml=2, this fix ensures correct
> behavior for specification compliance and future-proofing.
>
> The fix ensures all ml values 0-3 correctly use the 12 KB default, with
> only values 4+ using the formula ml * 4096.
>
> Reviewed-by: Harald Freudenberger <freude@linux.ibm.com>
> Signed-off-by: Finn Callies <fcallies@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260805092928.26932-1-fcallies@linux.ibm.com?part=1
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2 1/1] s390/ap: Fix MAPML computation
2026-08-05 9:29 [PATCH v2 1/1] s390/ap: Fix MAPML computation Finn Callies
2026-08-05 9:45 ` sashiko-bot
@ 2026-08-05 9:57 ` Heiko Carstens
2026-08-05 13:01 ` Vasily Gorbik
2 siblings, 0 replies; 4+ messages in thread
From: Heiko Carstens @ 2026-08-05 9:57 UTC (permalink / raw)
To: Finn Callies; +Cc: gor, agordeev, linux-s390, freude
On Wed, Aug 05, 2026 at 11:29:28AM +0200, Finn Callies wrote:
> When the TAPQ subfunction of PQAP returns a value between 0 and 3 in the
> ml field, the Principles of Operation states that the Maximum AP Message
> Length (MAPML) must be 12 KB.
>
> The previous code incorrectly calculated smaller sizes for ml values 1-2:
> - ml=1: 4 KB instead of 12 KB
> - ml=2: 8 KB instead of 12 KB
>
> While no current hardware reports ml=1 or ml=2, this fix ensures correct
> behavior for specification compliance and future-proofing.
>
> The fix ensures all ml values 0-3 correctly use the 12 KB default, with
> only values 4+ using the formula ml * 4096.
>
> Reviewed-by: Harald Freudenberger <freude@linux.ibm.com>
> Signed-off-by: Finn Callies <fcallies@linux.ibm.com>
> ---
> drivers/s390/crypto/ap_card.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Heiko Carstens <hca@linux.ibm.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2 1/1] s390/ap: Fix MAPML computation
2026-08-05 9:29 [PATCH v2 1/1] s390/ap: Fix MAPML computation Finn Callies
2026-08-05 9:45 ` sashiko-bot
2026-08-05 9:57 ` Heiko Carstens
@ 2026-08-05 13:01 ` Vasily Gorbik
2 siblings, 0 replies; 4+ messages in thread
From: Vasily Gorbik @ 2026-08-05 13:01 UTC (permalink / raw)
To: Finn Callies; +Cc: hca, agordeev, linux-s390, freude
On Wed, Aug 05, 2026 at 11:29:28AM +0200, Finn Callies wrote:
> When the TAPQ subfunction of PQAP returns a value between 0 and 3 in the
> ml field, the Principles of Operation states that the Maximum AP Message
> Length (MAPML) must be 12 KB.
>
> The previous code incorrectly calculated smaller sizes for ml values 1-2:
> - ml=1: 4 KB instead of 12 KB
> - ml=2: 8 KB instead of 12 KB
>
> While no current hardware reports ml=1 or ml=2, this fix ensures correct
> behavior for specification compliance and future-proofing.
>
> The fix ensures all ml values 0-3 correctly use the 12 KB default, with
> only values 4+ using the formula ml * 4096.
>
> Reviewed-by: Harald Freudenberger <freude@linux.ibm.com>
> Signed-off-by: Finn Callies <fcallies@linux.ibm.com>
> ---
> drivers/s390/crypto/ap_card.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thank you!
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2026-08-05 13:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-08-05 9:29 [PATCH v2 1/1] s390/ap: Fix MAPML computation Finn Callies
2026-08-05 9:45 ` sashiko-bot
2026-08-05 9:57 ` Heiko Carstens
2026-08-05 13:01 ` Vasily Gorbik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox