From: Harald Freudenberger <freude@linux.ibm.com>
To: dengler@linux.ibm.com, fcallies@linux.ibm.com
Cc: freude@linux.ibm.com, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: [PATCH v3 0/2] Support APMLM field with PQAP/TAPQ instruction
Date: Tue, 13 Oct 2026 15:44:20 +0200 [thread overview]
Message-ID: <20261013134422.64155-1-freude@linux.ibm.com> (raw)
There is a new field APMLM (AP message limit multiplier) defined
within the GR2 register on successful invocation of the TAPQ
subfunction for the PQAP instruction. This patch (series) covers all
what's needed to support this new field within the AP bus code.
Changelog:
v1: initial version
v2: The update of the bit mask TAPQ_CARD_HWINFO_MASK was missing. So
the new field apmlm could not shine through.
v3: Shashiko complained about that there is no upper limit but the
combination of apml and apmlm could lead to memory allocations of
960KB per AP request/reply. So introduce an upper and lower limit
to crop this firmware given AP message size limit into reasonable
range. By default 12KB...72KB but the upper limit can be adjusted
via module parameter.
Harald Freudenberger (2):
s390/ap: Support new APMLM field with PQAP/TAPQ instruction
s390/ap: Cap AP maximum message size adjustable via module parameter
arch/s390/include/asm/ap.h | 4 ++--
drivers/s390/crypto/ap_bus.c | 11 +++++++++++
drivers/s390/crypto/ap_bus.h | 7 +++++--
drivers/s390/crypto/ap_card.c | 9 ++++++++-
4 files changed, 26 insertions(+), 5 deletions(-)
--
2.43.0
next reply other threads:[~2026-10-13 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:44 Harald Freudenberger [this message]
2026-10-13 13:44 ` [PATCH v3 1/2] s390/ap: Support new APMLM field with PQAP/TAPQ instruction Harald Freudenberger
2026-10-13 13:52 ` sashiko-bot
2026-10-13 13:44 ` [PATCH v3 2/2] s390/ap: Cap AP maximum message size adjustable via module parameter Harald Freudenberger
2026-10-13 13:52 ` sashiko-bot
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=20261013134422.64155-1-freude@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox