From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC v2 PATCH 0/4] ARM[64]: kernel mode NEON in atomic contexts
Date: Wed, 9 Oct 2013 20:50:30 +0200 [thread overview]
Message-ID: <1381344634-14917-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This is another stab at a way to enable the use of NEON in atomic
context. As suggested by Nico, all there is to it is basically to
stack the registers you are about to use, and unstack them when you're
done.
Patches #1 and #2 implement this for ARM and ARM64 respectively, #3 and #4
are the examples I posted earlier adapted to use this new method.
Ard Biesheuvel (4):
ARM: add support for kernel mode NEON in atomic context
ARM64: add support for kernel mode NEON in atomic context
ARM64: add Crypto Extensions based synchronous core AES cipher
ARM64: add Crypto Extensions based synchronous AES in CCM mode
arch/arm/include/asm/fpstate.h | 15 +-
arch/arm/include/asm/neon.h | 34 +++
arch/arm/vfp/vfphw.S | 46 ++++
arch/arm/vfp/vfpmodule.c | 3 +
arch/arm64/crypto/Makefile | 12 +
arch/arm64/crypto/aes-sync.c | 453 ++++++++++++++++++++++++++++++++++
arch/arm64/crypto/aesce-ccm.S | 154 ++++++++++++
arch/arm64/include/asm/fpsimd.h | 16 ++
arch/arm64/include/asm/fpsimdmacros.h | 37 +++
arch/arm64/include/asm/neon.h | 31 +++
arch/arm64/kernel/entry-fpsimd.S | 24 ++
arch/arm64/kernel/fpsimd.c | 3 +
12 files changed, 827 insertions(+), 1 deletion(-)
create mode 100644 arch/arm64/crypto/Makefile
create mode 100644 arch/arm64/crypto/aes-sync.c
create mode 100644 arch/arm64/crypto/aesce-ccm.S
--
1.8.1.2
next reply other threads:[~2013-10-09 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 18:50 Ard Biesheuvel [this message]
2013-10-09 18:50 ` [RFC v2 PATCH 1/4] ARM: add support for kernel mode NEON in atomic context Ard Biesheuvel
2013-10-09 19:24 ` Nicolas Pitre
2013-10-09 19:32 ` Ard Biesheuvel
2013-10-10 3:45 ` Nicolas Pitre
2013-10-09 18:50 ` [RFC v2 PATCH 2/4] ARM64: " Ard Biesheuvel
2013-10-11 17:14 ` Catalin Marinas
2013-10-11 17:30 ` Ard Biesheuvel
2013-10-11 19:35 ` Catalin Marinas
2013-10-11 20:09 ` Nicolas Pitre
2013-10-13 22:48 ` Catalin Marinas
2013-10-14 8:12 ` Ard Biesheuvel
2013-10-09 18:50 ` [RFC v2 PATCH 3/4] ARM64: add Crypto Extensions based synchronous core AES cipher Ard Biesheuvel
2013-10-09 18:50 ` [RFC v2 PATCH 4/4] ARM64: add Crypto Extensions based synchronous AES in CCM mode Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2013-10-09 18:49 [RFC v2 PATCH 0/4] ARM[64]: kernel mode NEON in atomic contexts Ard Biesheuvel
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=1381344634-14917-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--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).