Linux s390 Architecture development
 help / color / mirror / Atom feed
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, linux-s390@vger.kernel.org,
	dengler@linux.ibm.com, borntraeger@linux.ibm.com,
	fcallies@linux.ibm.com, cohuck@redhat.com
Subject: Re: [PATCH v14 07/19] target/s390x: Support AES ECB for cpacf km instruction
Date: Mon, 17 Aug 2026 17:55:42 +0200	[thread overview]
Message-ID: <cded574a75e8bec52fd9492d60cc1c6d@linux.ibm.com> (raw)
In-Reply-To: <6621b094-e536-4f47-8b69-c9c0ad4132f8@linux.ibm.com>

On 2026-08-17 10:11, Ilya Leoshkevich wrote:
> On 8/6/26 17:12, Harald Freudenberger wrote:
>> Support the subfunctions CPACF_KM_AES_128, CPACF_KM_AES_192
>> and CPACF_KM_AES_256 for the cpacf km instruction.
>> 
>> Tested-by: Holger Dengler <dengler@linux.ibm.com>
>> Reviewed-by: Finn Callies <fcallies@linux.ibm.com>
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>> ---
>>   target/s390x/gen-features.c      |   3 +
>>   target/s390x/tcg/cpacf.h         |   6 ++
>>   target/s390x/tcg/cpacf_aes.c     | 107 
>> +++++++++++++++++++++++++++++++
>>   target/s390x/tcg/crypto_helper.c |  24 +++++++
>>   target/s390x/tcg/meson.build     |   1 +
>>   5 files changed, 141 insertions(+)
>>   create mode 100644 target/s390x/tcg/cpacf_aes.c
>> 
> 
> [...]
> 
>> +/*
>> + * read exactly one AES block from guest memory into a local buffer
>> + */
>> +static inline void aes_read_block(CPUS390XState *env, const int 
>> mmu_idx,
>> +                                  const uintptr_t ra, uint64_t 
>> guest_addr,
>> +                                  uint8_t *buf)
>> +{
>> +    read_guest_wrap_u8(env, mmu_idx, ra, guest_addr, buf, 
>> AES_BLOCK_SIZE);
>> +}
>> +
>> +/*
>> + * write exactly one AES block from local buffer to guest memory
>> + */
>> +static void aes_write_block(CPUS390XState *env, const int mmu_idx,
>> +                            const uintptr_t ra, uint64_t guest_addr,
>> +                            uint8_t *buf)
>> +{
>> +    write_guest_wrap_u8(env, mmu_idx, ra, guest_addr, buf, 
>> AES_BLOCK_SIZE);
>> +}
> 
> nit: I would these two functions, I don't think they deserve a wrapper.
> 

I'd like to keep these two wrappers: The code is much more readable (for 
my
feeling) and the compiler hopefully does his job and replace it anyway.

>> +
>> +int cpacf_aes_ecb(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];
>> +    uint64_t len = *src_len_reg, done = 0;
>> +    int i, keysize, addr_reg_size = 64;
>> +    uint8_t key[32];
>> +    AES_KEY exkey;
>> +
>> +    g_assert(type == S390_FEAT_TYPE_KM);
>> +    switch (fc) {
>> +    case CPACF_KM_AES_128:
>> +        keysize = 16;
>> +        break;
>> +    case CPACF_KM_AES_192:
>> +        keysize = 24;
>> +        break;
>> +    case CPACF_KM_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 key from param block */
>> +    read_guest_wrap_u8(env, mmu_idx, ra, param_addr, key, keysize);
>> +
>> +    /* 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, ra, *src_ptr_reg + done, in);
>> +        if (mod) {
>> +            AES_decrypt(in, out, &exkey);
>> +        } else {
>> +            AES_encrypt(in, out, &exkey);
>> +        }
>> +        aes_write_block(env, mmu_idx, ra, *dst_ptr_reg + done, out);
>> +        len -= AES_BLOCK_SIZE;
>> +        done += AES_BLOCK_SIZE;
>> +    }
>> +
>> +    *src_ptr_reg = deposit64(*src_ptr_reg, 0, addr_reg_size,
>> +                             *src_ptr_reg + done);
>> +    *dst_ptr_reg = deposit64(*dst_ptr_reg, 0, addr_reg_size,
>> +                             *dst_ptr_reg + done);
>> +    *src_len_reg -= done;
>> +
>> +    return !len ? 0 : 3;
>> +}
> 
> The issue with writing memory, but not registers, on fault is still
> there, but I think today's behavior is good enough for emulating real
> sane code.
> 

I have opened up bugzilla 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=221910 to track this.
But it will not be part of this patch series.

> 
> With our without the above addressed:
> 
> Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>

  reply	other threads:[~2026-08-17 15:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 15:12 [PATCH v14 00/19] target/s390x: Extend qemu CPACF support Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 01/19] target/s390x: Fix missing privileged flag at PCKMO instruction Harald Freudenberger
2026-08-06 18:48   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 02/19] target/s390x: Rework s390 cpacf implementations Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 03/19] target/s390x: Move cpacf sha512 code into a new file Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 04/19] target/s390x: Support cpacf sha256 Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 05/19] target/s390x: Add helper functions for copy memory to and from guest Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 06/19] crypto: Add aes-helpers file to support some AES modes Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 07/19] target/s390x: Support AES ECB for cpacf km instruction Harald Freudenberger
2026-08-17  8:11   ` Ilya Leoshkevich
2026-08-17 15:55     ` Harald Freudenberger [this message]
2026-08-17  9:17   ` Ilya Leoshkevich
2026-08-17 14:23     ` Harald Freudenberger
2026-08-17 15:00       ` Ilya Leoshkevich
2026-08-18 10:34         ` Harald Freudenberger
2026-08-18 11:31           ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 08/19] target/s390x: Support AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 09/19] target/s390x: Support AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-06 15:12 ` [PATCH v14 10/19] target/s390x: Minimal AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-17  8:16   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 11/19] target/s390x: Support AES XTS for cpacf km instruction Harald Freudenberger
2026-08-17  8:20   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 12/19] target/s390x: Base support for cpacf protected keys and pckmo Harald Freudenberger
2026-08-17  8:25   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 13/19] target/s390x: Support protected key AES ECB for cpacf km instruction Harald Freudenberger
2026-08-17  8:26   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 14/19] target/s390x: Support protected key AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-17  8:27   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 15/19] target/s390x: Support protected key AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-17  8:28   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 16/19] target/s390x: Minimal protected key AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-17  8:46   ` Ilya Leoshkevich
2026-08-06 15:12 ` [PATCH v14 17/19] target/s390x: Support protected key AES XTS for cpacf km instruction Harald Freudenberger
2026-08-17  9:00   ` Ilya Leoshkevich
2026-08-06 15:13 ` [PATCH v14 18/19] docs/s390: Document CPACF instructions support Harald Freudenberger
2026-08-06 15:13 ` [PATCH v14 19/19] tests/tcg/s390x: Add tests for CPACF instructions Harald Freudenberger
2026-08-17  9:02   ` Ilya Leoshkevich

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=cded574a75e8bec52fd9492d60cc1c6d@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=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