From: Harald Freudenberger <freude@linux.ibm.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>
Cc: richard.henderson@linaro.org, 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 06/18] target/s390x: Support AES CBC for cpacf kmc instruction
Date: Tue, 30 Jun 2026 15:59:45 +0200 [thread overview]
Message-ID: <81ddd4d2d7c3912704c41db6bd2bf453@linux.ibm.com> (raw)
In-Reply-To: <193565c3-6215-4dd7-bb99-4410ed48196f@linux.ibm.com>
On 2026-06-24 19:22, Ilya Leoshkevich wrote:
> On 6/24/26 10:10, Harald Freudenberger wrote:
>> Support the subfunctions CPACF_KMC_AES_128, CPACF_KMC_AES_192
>> and CPACF_KMC_AES_256 for the cpacf kmc instruction.
>>
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>> Tested-by: Holger Dengler <dengler@linux.ibm.com>
>> Reviewed-by: Finn Callies <fcallies@linux.ibm.com>
>> ---
>> target/s390x/gen-features.c | 3 +
>> target/s390x/tcg/cpacf.h | 4 ++
>> target/s390x/tcg/cpacf_aes.c | 102
>> +++++++++++++++++++++++++++++++
>> target/s390x/tcg/crypto_helper.c | 24 ++++++++
>> 4 files changed, 133 insertions(+)
>
> [...]
>
>> diff --git a/target/s390x/tcg/cpacf_aes.c
>> b/target/s390x/tcg/cpacf_aes.c
>> index ba836f1473..6412cc187d 100644
>> --- a/target/s390x/tcg/cpacf_aes.c
>> +++ b/target/s390x/tcg/cpacf_aes.c
>> @@ -111,3 +111,105 @@ int cpacf_aes_ecb(CPUS390XState *env, const int
>> mmu_idx, uintptr_t ra,
>> return !len ? 0 : 3;
>> }
>> +
>> +static void aes_xor(const uint8_t *src1, const uint8_t *src2, uint8_t
>> *dst)
>> +{
>> + for (int i = 0; i < AES_BLOCK_SIZE; i++) {
>> + dst[i] = src1[i] ^ src2[i];
>> + }
>> +}
>> +
>> +int cpacf_aes_cbc(CPUS390XState *env, const int mmu_idx, uintptr_t
>> ra,
>> + uint64_t param_addr, uint64_t *dst_ptr_reg,
>> + uint64_t *src_ptr_reg, uint64_t *src_len_reg,
>> + uint32_t type, uint8_t fc, uint8_t mod)
>> +{
>> + enum { MAX_BLOCKS_PER_RUN = 8192 / AES_BLOCK_SIZE };
>> + uint8_t in[AES_BLOCK_SIZE], out[AES_BLOCK_SIZE],
>> buf[AES_BLOCK_SIZE];
>> + const MemOpIdx oi = make_memop_idx(MO_8, mmu_idx);
>> + uint64_t addr, len = *src_len_reg, done = 0;
>> + int i, keysize, addr_reg_size = 64;
>> + uint8_t key[32], iv[AES_BLOCK_SIZE];
>> + AES_KEY exkey;
>> +
>> + g_assert(type == S390_FEAT_TYPE_KMC);
>> +
>> + switch (fc) {
>> + case 0x12: /* CPACF_KMC_AES_128 */
>> + keysize = 16;
>> + break;
>> + case 0x13: /* CPACF_KMC_AES_192 */
>> + keysize = 24;
>> + break;
>> + case 0x14: /* CPACF_KMC_AES_256 */
>> + keysize = 32;
>> + break;
>> + default:
>> + g_assert_not_reached();
>> + }
>> +
>> + if (!(env->psw.mask & PSW_MASK_64)) {
>> + len = (uint32_t)len;
>> + addr_reg_size = (env->psw.mask & PSW_MASK_32) ? 32 : 24;
>> + }
>> +
>> + /* length has to be properly aligned. */
>> + if (!QEMU_IS_ALIGNED(len, AES_BLOCK_SIZE)) {
>> + tcg_s390_program_interrupt(env, PGM_SPECIFICATION, ra);
>> + }
>> +
>> + /* fetch iv from param block */
>> + for (i = 0; i < AES_BLOCK_SIZE; i++) {
>> + addr = wrap_address(env, param_addr + i);
>> + iv[i] = cpu_ldb_mmu(env, addr, oi, ra);
>> + }
>> +
>> + /* fetch key from param block */
>> + for (i = 0; i < keysize; i++) {
>> + addr = wrap_address(env, param_addr + AES_BLOCK_SIZE + i);
>> + key[i] = cpu_ldb_mmu(env, addr, oi, ra);
>> + }
>
> Another couple of candidates for copy_from_guest_wrap().
>
Yes, makes sense to have some (inline) function. I think I will add
something to cpacf.h.
>> +
>> + /* expand key */
>> + if (mod) {
>> + AES_set_decrypt_key(key, keysize * 8, &exkey);
>> + } else {
>> + AES_set_encrypt_key(key, keysize * 8, &exkey);
>> + }
>> +
>> + /* process up to MAX_BLOCKS_PER_RUN aes blocks */
>> + for (i = 0; i < MAX_BLOCKS_PER_RUN && len >= AES_BLOCK_SIZE; i++)
>> {
>> + aes_read_block(env, mmu_idx, *src_ptr_reg + done, in, ra);
>> + if (mod) {
>> + /* decrypt in => buf */
>> + AES_decrypt(in, buf, &exkey);
>> + /* buf xor iv => out */
>> + aes_xor(buf, iv, out);
>> + /* prep iv for next round */
>> + memcpy(iv, in, AES_BLOCK_SIZE);
>> + } else {
>> + /* in xor iv => buf */
>> + aes_xor(in, iv, buf);
>> + /* encrypt buf => out */
>> + AES_encrypt(buf, out, &exkey);
>> + /* prep iv for next round */
>> + memcpy(iv, out, AES_BLOCK_SIZE);
>> + }
>> + aes_write_block(env, mmu_idx, *dst_ptr_reg + done, out, ra);
>> + len -= AES_BLOCK_SIZE, done += AES_BLOCK_SIZE;
>
> I think
>
> len -= AES_BLOCK_SIZE;
> done += AES_BLOCK_SIZE;
>
> would be clearer.
>
>
> Other than that:
>
> Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>
>
> [...]
next prev parent reply other threads:[~2026-06-30 13:59 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
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 [this message]
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=81ddd4d2d7c3912704c41db6bd2bf453@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=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