From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [GIT PULL] libcrypto/arm64: Move kernel mode FP/SIMD buffer to the stack
Date: Wed, 12 Nov 2025 12:53:02 -0800 [thread overview]
Message-ID: <20251112205302.GB1760@sol> (raw)
In-Reply-To: <20251112093212.2392848-2-ardb+git@google.com>
On Wed, Nov 12, 2025 at 10:32:13AM +0100, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> Hi Eric,
>
> (cc Catalin)
>
> I have prepared a branch for libcrypto-next containing all the arm64 FP/SIMD
> changes that are needed to move the kernel mode FP/SIMD buffers to the stack.
>
> I have created two stable tags [a] and [b] in my tree at [0], containing the
> changes as sent to and reviewed on the list, reordered to accommodate the task
> of merging this into libcrypto-next in a bisectable manner.
>
> [a] scoped-ksimd-for-arm-arm64
> [b] arm64-fpsimd-on-stack-for-v6.19
>
> On top of [a], two additional lib/crypto patches have been applied to update
> code that has already been queued up in libcrypto-next, moving it to the new
> scoped ksimd API as well. This is better than hiding the changes in a merge
> commit. The merge still resulted in a conflict on the old versions of the files
> that were moved, but this is resolved by simply deleting them.
>
> Please pull. Or alternatively, if you prefer, recreate the following sequence
> directly on top of libcrypto-next (and resolve the conflict)
>
> Merge tag 'ardb/scoped-ksimd-for-arm-arm64'
> lib/crypto: arm/blake2b: Move to scoped ksimd API
> lib/crypto: arm64: Move remaining algorithms to scoped ksimd API
> Merge tag 'arm64-fpsimd-on-stack-for-v6.19' into arm64-fpsimd-on-stack-for-libcrypto
>
> The following changes since commit f101371e1972df3d897bf2326eda3c28aca2e58c:
>
> Merge remote-tracking branch 'ebiggers/libcrypto-aes-gcm' into libcrypto-next (2025-11-11 11:08:57 -0800)
>
> are available in the Git repository at:
>
> [0] git://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git arm64-fpsimd-on-stack-for-libcrypto
>
> for you to fetch changes up to 82ef0a6ac77cc0eaca1b5c2fc3436b18cda6ef83:
>
> Merge tag 'arm64-fpsimd-on-stack-for-v6.19' into arm64-fpsimd-on-stack-for-libcrypto (2025-11-12 10:08:20 +0100)
I pulled these into a libcrypto-fpsimd-on-stack branch based on
2dbb6f4a25d38fcf (which is currently the last commit that I'm planning
for the "main" libcrypto pull request).
Then I updated the head of libcrypto-next to be the merge of
libcrypto-tests, libcrypto-aes-gcm, and libcrypto-fpsimd-on-stack. I'll
send these as separate pull requests after the main libcrypto one.
In theory this should all work out.
Note: I changed "lib/crypto: arm64: Move remaining algorithms to scoped
ksimd API" to remove <asm/neon.h> from lib/crypto/arm64/polyval.h for
consistency with the other files, and to add braces around the for loop.
Thanks!
- Eric
prev parent reply other threads:[~2025-11-12 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 9:32 [GIT PULL] libcrypto/arm64: Move kernel mode FP/SIMD buffer to the stack Ard Biesheuvel
2025-11-12 20:53 ` Eric Biggers [this message]
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=20251112205302.GB1760@sol \
--to=ebiggers@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).