2019-06-04 11:11:33 +03:00
|
|
|
/* SPDX-License-Identifier: GPL-2.0-only */
|
2014-03-21 13:19:17 +04:00
|
|
|
/*
|
|
|
|
|
* linux/arch/arm64/crypto/aes-modes.S - chaining mode wrappers for AES
|
|
|
|
|
*
|
2017-02-03 17:49:37 +03:00
|
|
|
* Copyright (C) 2013 - 2017 Linaro Ltd <ard.biesheuvel@linaro.org>
|
2014-03-21 13:19:17 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
/* included by aes-ce.S and aes-neon.S */
|
|
|
|
|
|
|
|
|
|
.text
|
|
|
|
|
.align 4
|
|
|
|
|
|
2019-06-24 20:38:30 +03:00
|
|
|
#ifndef MAX_STRIDE
|
|
|
|
|
#define MAX_STRIDE 4
|
|
|
|
|
#endif
|
|
|
|
|
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
#if MAX_STRIDE == 4
|
|
|
|
|
#define ST4(x...) x
|
|
|
|
|
#define ST5(x...)
|
|
|
|
|
#else
|
|
|
|
|
#define ST4(x...)
|
|
|
|
|
#define ST5(x...) x
|
|
|
|
|
#endif
|
|
|
|
|
|
2014-03-21 13:19:17 +04:00
|
|
|
aes_encrypt_block4x:
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block4x v0, v1, v2, v3, w3, x2, x8, w7
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
ENDPROC(aes_encrypt_block4x)
|
|
|
|
|
|
|
|
|
|
aes_decrypt_block4x:
|
2018-09-10 17:41:13 +03:00
|
|
|
decrypt_block4x v0, v1, v2, v3, w3, x2, x8, w7
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
ENDPROC(aes_decrypt_block4x)
|
|
|
|
|
|
2019-06-24 20:38:30 +03:00
|
|
|
#if MAX_STRIDE == 5
|
|
|
|
|
aes_encrypt_block5x:
|
|
|
|
|
encrypt_block5x v0, v1, v2, v3, v4, w3, x2, x8, w7
|
|
|
|
|
ret
|
|
|
|
|
ENDPROC(aes_encrypt_block5x)
|
|
|
|
|
|
|
|
|
|
aes_decrypt_block5x:
|
|
|
|
|
decrypt_block5x v0, v1, v2, v3, v4, w3, x2, x8, w7
|
|
|
|
|
ret
|
|
|
|
|
ENDPROC(aes_decrypt_block5x)
|
|
|
|
|
#endif
|
|
|
|
|
|
2014-03-21 13:19:17 +04:00
|
|
|
/*
|
|
|
|
|
* aes_ecb_encrypt(u8 out[], u8 const in[], u8 const rk[], int rounds,
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
* int blocks)
|
2014-03-21 13:19:17 +04:00
|
|
|
* aes_ecb_decrypt(u8 out[], u8 const in[], u8 const rk[], int rounds,
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
* int blocks)
|
2014-03-21 13:19:17 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ecb_encrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
2014-03-21 13:19:17 +04:00
|
|
|
|
2018-09-10 17:41:13 +03:00
|
|
|
enc_prepare w3, x2, x5
|
2014-03-21 13:19:17 +04:00
|
|
|
|
|
|
|
|
.LecbencloopNx:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
subs w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lecbenc1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 pt blocks */
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST4( bl aes_encrypt_block4x )
|
|
|
|
|
ST5( ld1 {v4.16b}, [x1], #16 )
|
|
|
|
|
ST5( bl aes_encrypt_block5x )
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( st1 {v4.16b}, [x0], #16 )
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LecbencloopNx
|
|
|
|
|
.Lecbenc1x:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
adds w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lecbencout
|
|
|
|
|
.Lecbencloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b}, [x1], #16 /* get next pt block */
|
|
|
|
|
encrypt_block v0, w3, x2, x5, w6
|
|
|
|
|
st1 {v0.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
bne .Lecbencloop
|
|
|
|
|
.Lecbencout:
|
2018-09-10 17:41:13 +03:00
|
|
|
ldp x29, x30, [sp], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_ecb_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ecb_decrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
2018-04-30 19:18:24 +03:00
|
|
|
|
2018-09-10 17:41:13 +03:00
|
|
|
dec_prepare w3, x2, x5
|
2014-03-21 13:19:17 +04:00
|
|
|
|
|
|
|
|
.LecbdecloopNx:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
subs w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lecbdec1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 ct blocks */
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST4( bl aes_decrypt_block4x )
|
|
|
|
|
ST5( ld1 {v4.16b}, [x1], #16 )
|
|
|
|
|
ST5( bl aes_decrypt_block5x )
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( st1 {v4.16b}, [x0], #16 )
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LecbdecloopNx
|
|
|
|
|
.Lecbdec1x:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
adds w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lecbdecout
|
|
|
|
|
.Lecbdecloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b}, [x1], #16 /* get next ct block */
|
|
|
|
|
decrypt_block v0, w3, x2, x5, w6
|
|
|
|
|
st1 {v0.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
bne .Lecbdecloop
|
|
|
|
|
.Lecbdecout:
|
2018-09-10 17:41:13 +03:00
|
|
|
ldp x29, x30, [sp], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_ecb_decrypt)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* aes_cbc_encrypt(u8 out[], u8 const in[], u8 const rk[], int rounds,
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
* int blocks, u8 iv[])
|
2014-03-21 13:19:17 +04:00
|
|
|
* aes_cbc_decrypt(u8 out[], u8 const in[], u8 const rk[], int rounds,
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
* int blocks, u8 iv[])
|
2014-03-21 13:19:17 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_encrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v4.16b}, [x5] /* get iv */
|
|
|
|
|
enc_prepare w3, x2, x6
|
2014-03-21 13:19:17 +04:00
|
|
|
|
2018-03-10 18:21:52 +03:00
|
|
|
.Lcbcencloop4x:
|
2018-09-10 17:41:13 +03:00
|
|
|
subs w4, w4, #4
|
2018-03-10 18:21:52 +03:00
|
|
|
bmi .Lcbcenc1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 pt blocks */
|
2018-03-10 18:21:52 +03:00
|
|
|
eor v0.16b, v0.16b, v4.16b /* ..and xor with iv */
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v0, w3, x2, x6, w7
|
2018-03-10 18:21:52 +03:00
|
|
|
eor v1.16b, v1.16b, v0.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v1, w3, x2, x6, w7
|
2018-03-10 18:21:52 +03:00
|
|
|
eor v2.16b, v2.16b, v1.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v2, w3, x2, x6, w7
|
2018-03-10 18:21:52 +03:00
|
|
|
eor v3.16b, v3.16b, v2.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v3, w3, x2, x6, w7
|
|
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
2018-03-10 18:21:52 +03:00
|
|
|
mov v4.16b, v3.16b
|
|
|
|
|
b .Lcbcencloop4x
|
|
|
|
|
.Lcbcenc1x:
|
2018-09-10 17:41:13 +03:00
|
|
|
adds w4, w4, #4
|
2018-03-10 18:21:52 +03:00
|
|
|
beq .Lcbcencout
|
|
|
|
|
.Lcbcencloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b}, [x1], #16 /* get next pt block */
|
2018-03-10 18:21:52 +03:00
|
|
|
eor v4.16b, v4.16b, v0.16b /* ..and xor with iv */
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v4, w3, x2, x6, w7
|
|
|
|
|
st1 {v4.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
bne .Lcbcencloop
|
2018-03-10 18:21:52 +03:00
|
|
|
.Lcbcencout:
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v4.16b}, [x5] /* return iv */
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_cbc_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_decrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
2014-03-21 13:19:17 +04:00
|
|
|
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ld1 {cbciv.16b}, [x5] /* get iv */
|
2018-09-10 17:41:13 +03:00
|
|
|
dec_prepare w3, x2, x6
|
2014-03-21 13:19:17 +04:00
|
|
|
|
|
|
|
|
.LcbcdecloopNx:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
subs w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lcbcdec1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 ct blocks */
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
#if MAX_STRIDE == 5
|
|
|
|
|
ld1 {v4.16b}, [x1], #16 /* get 1 ct block */
|
|
|
|
|
mov v5.16b, v0.16b
|
|
|
|
|
mov v6.16b, v1.16b
|
|
|
|
|
mov v7.16b, v2.16b
|
|
|
|
|
bl aes_decrypt_block5x
|
|
|
|
|
sub x1, x1, #32
|
|
|
|
|
eor v0.16b, v0.16b, cbciv.16b
|
|
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
|
ld1 {v5.16b}, [x1], #16 /* reload 1 ct block */
|
|
|
|
|
ld1 {cbciv.16b}, [x1], #16 /* reload 1 ct block */
|
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
|
|
|
|
eor v3.16b, v3.16b, v7.16b
|
|
|
|
|
eor v4.16b, v4.16b, v5.16b
|
|
|
|
|
#else
|
2014-03-21 13:19:17 +04:00
|
|
|
mov v4.16b, v0.16b
|
|
|
|
|
mov v5.16b, v1.16b
|
|
|
|
|
mov v6.16b, v2.16b
|
2018-03-10 18:21:51 +03:00
|
|
|
bl aes_decrypt_block4x
|
2018-09-10 17:41:13 +03:00
|
|
|
sub x1, x1, #16
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
eor v0.16b, v0.16b, cbciv.16b
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v1.16b, v1.16b, v4.16b
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ld1 {cbciv.16b}, [x1], #16 /* reload 1 ct block */
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v2.16b, v2.16b, v5.16b
|
|
|
|
|
eor v3.16b, v3.16b, v6.16b
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
#endif
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( st1 {v4.16b}, [x0], #16 )
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LcbcdecloopNx
|
|
|
|
|
.Lcbcdec1x:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
adds w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lcbcdecout
|
|
|
|
|
.Lcbcdecloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v1.16b}, [x1], #16 /* get next ct block */
|
2014-03-21 13:19:17 +04:00
|
|
|
mov v0.16b, v1.16b /* ...and copy to v0 */
|
2018-09-10 17:41:13 +03:00
|
|
|
decrypt_block v0, w3, x2, x6, w7
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
eor v0.16b, v0.16b, cbciv.16b /* xor with iv => pt */
|
|
|
|
|
mov cbciv.16b, v1.16b /* ct is next iv */
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
bne .Lcbcdecloop
|
|
|
|
|
.Lcbcdecout:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
st1 {cbciv.16b}, [x5] /* return iv */
|
2018-09-10 17:41:13 +03:00
|
|
|
ldp x29, x30, [sp], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_cbc_decrypt)
|
|
|
|
|
|
|
|
|
|
|
2018-09-10 17:41:14 +03:00
|
|
|
/*
|
|
|
|
|
* aes_cbc_cts_encrypt(u8 out[], u8 const in[], u32 const rk[],
|
|
|
|
|
* int rounds, int bytes, u8 const iv[])
|
|
|
|
|
* aes_cbc_cts_decrypt(u8 out[], u8 const in[], u32 const rk[],
|
|
|
|
|
* int rounds, int bytes, u8 const iv[])
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_cts_encrypt)
|
|
|
|
|
adr_l x8, .Lcts_permute_table
|
|
|
|
|
sub x4, x4, #16
|
|
|
|
|
add x9, x8, #32
|
|
|
|
|
add x8, x8, x4
|
|
|
|
|
sub x9, x9, x4
|
|
|
|
|
ld1 {v3.16b}, [x8]
|
|
|
|
|
ld1 {v4.16b}, [x9]
|
|
|
|
|
|
|
|
|
|
ld1 {v0.16b}, [x1], x4 /* overlapping loads */
|
|
|
|
|
ld1 {v1.16b}, [x1]
|
|
|
|
|
|
|
|
|
|
ld1 {v5.16b}, [x5] /* get iv */
|
|
|
|
|
enc_prepare w3, x2, x6
|
|
|
|
|
|
|
|
|
|
eor v0.16b, v0.16b, v5.16b /* xor with iv */
|
|
|
|
|
tbl v1.16b, {v1.16b}, v4.16b
|
|
|
|
|
encrypt_block v0, w3, x2, x6, w7
|
|
|
|
|
|
|
|
|
|
eor v1.16b, v1.16b, v0.16b
|
|
|
|
|
tbl v0.16b, {v0.16b}, v3.16b
|
|
|
|
|
encrypt_block v1, w3, x2, x6, w7
|
|
|
|
|
|
|
|
|
|
add x4, x0, x4
|
|
|
|
|
st1 {v0.16b}, [x4] /* overlapping stores */
|
|
|
|
|
st1 {v1.16b}, [x0]
|
|
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_cbc_cts_encrypt)
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_cts_decrypt)
|
|
|
|
|
adr_l x8, .Lcts_permute_table
|
|
|
|
|
sub x4, x4, #16
|
|
|
|
|
add x9, x8, #32
|
|
|
|
|
add x8, x8, x4
|
|
|
|
|
sub x9, x9, x4
|
|
|
|
|
ld1 {v3.16b}, [x8]
|
|
|
|
|
ld1 {v4.16b}, [x9]
|
|
|
|
|
|
|
|
|
|
ld1 {v0.16b}, [x1], x4 /* overlapping loads */
|
|
|
|
|
ld1 {v1.16b}, [x1]
|
|
|
|
|
|
|
|
|
|
ld1 {v5.16b}, [x5] /* get iv */
|
|
|
|
|
dec_prepare w3, x2, x6
|
|
|
|
|
|
|
|
|
|
tbl v2.16b, {v1.16b}, v4.16b
|
|
|
|
|
decrypt_block v0, w3, x2, x6, w7
|
|
|
|
|
eor v2.16b, v2.16b, v0.16b
|
|
|
|
|
|
|
|
|
|
tbx v0.16b, {v1.16b}, v4.16b
|
|
|
|
|
tbl v2.16b, {v2.16b}, v3.16b
|
|
|
|
|
decrypt_block v0, w3, x2, x6, w7
|
|
|
|
|
eor v0.16b, v0.16b, v5.16b /* xor with iv */
|
|
|
|
|
|
|
|
|
|
add x4, x0, x4
|
|
|
|
|
st1 {v2.16b}, [x4] /* overlapping stores */
|
|
|
|
|
st1 {v0.16b}, [x0]
|
|
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_cbc_cts_decrypt)
|
|
|
|
|
|
|
|
|
|
.section ".rodata", "a"
|
|
|
|
|
.align 6
|
|
|
|
|
.Lcts_permute_table:
|
|
|
|
|
.byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
|
|
|
|
|
.byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
|
|
|
|
|
.byte 0x0, 0x1, 0x2, 0x3, 0x4, 0x5, 0x6, 0x7
|
|
|
|
|
.byte 0x8, 0x9, 0xa, 0xb, 0xc, 0xd, 0xe, 0xf
|
|
|
|
|
.byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
|
|
|
|
|
.byte 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff, 0xff
|
|
|
|
|
.previous
|
|
|
|
|
|
|
|
|
|
|
2014-03-21 13:19:17 +04:00
|
|
|
/*
|
|
|
|
|
* aes_ctr_encrypt(u8 out[], u8 const in[], u8 const rk[], int rounds,
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
* int blocks, u8 ctr[])
|
2014-03-21 13:19:17 +04:00
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ctr_encrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
|
2018-09-10 17:41:13 +03:00
|
|
|
enc_prepare w3, x2, x6
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ld1 {vctr.16b}, [x5]
|
2017-01-17 16:46:29 +03:00
|
|
|
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
umov x6, vctr.d[1] /* keep swabbed ctr in reg */
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
rev x6, x6
|
2018-09-10 17:41:13 +03:00
|
|
|
cmn w6, w4 /* 32 bit overflow? */
|
|
|
|
|
bcs .Lctrloop
|
2014-03-21 13:19:17 +04:00
|
|
|
.LctrloopNx:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
subs w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lctr1x
|
2018-08-23 19:48:45 +03:00
|
|
|
add w7, w6, #1
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
mov v0.16b, vctr.16b
|
2018-08-23 19:48:45 +03:00
|
|
|
add w8, w6, #2
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
mov v1.16b, vctr.16b
|
|
|
|
|
add w9, w6, #3
|
|
|
|
|
mov v2.16b, vctr.16b
|
2018-08-23 19:48:45 +03:00
|
|
|
add w9, w6, #3
|
|
|
|
|
rev w7, w7
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
mov v3.16b, vctr.16b
|
2018-08-23 19:48:45 +03:00
|
|
|
rev w8, w8
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( mov v4.16b, vctr.16b )
|
2018-08-23 19:48:45 +03:00
|
|
|
mov v1.s[3], w7
|
|
|
|
|
rev w9, w9
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( add w10, w6, #4 )
|
2018-08-23 19:48:45 +03:00
|
|
|
mov v2.s[3], w8
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( rev w10, w10 )
|
2018-08-23 19:48:45 +03:00
|
|
|
mov v3.s[3], w9
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( mov v4.s[3], w10 )
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v5.16b-v7.16b}, [x1], #48 /* get 3 input blocks */
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST4( bl aes_encrypt_block4x )
|
|
|
|
|
ST5( bl aes_encrypt_block5x )
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v5.16b, v0.16b
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST4( ld1 {v5.16b}, [x1], #16 )
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v1.16b, v6.16b, v1.16b
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( ld1 {v5.16b-v6.16b}, [x1], #32 )
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v2.16b, v7.16b, v2.16b
|
|
|
|
|
eor v3.16b, v5.16b, v3.16b
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( eor v4.16b, v6.16b, v4.16b )
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ST5( st1 {v4.16b}, [x0], #16 )
|
|
|
|
|
add x6, x6, #MAX_STRIDE
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
rev x7, x6
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ins vctr.d[1], x7
|
2018-09-10 17:41:13 +03:00
|
|
|
cbz w4, .Lctrout
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LctrloopNx
|
|
|
|
|
.Lctr1x:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
adds w4, w4, #MAX_STRIDE
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lctrout
|
|
|
|
|
.Lctrloop:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
mov v0.16b, vctr.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v0, w3, x2, x8, w7
|
2017-01-17 16:46:29 +03:00
|
|
|
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
adds x6, x6, #1 /* increment BE ctr */
|
|
|
|
|
rev x7, x6
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ins vctr.d[1], x7
|
2017-01-17 16:46:29 +03:00
|
|
|
bcs .Lctrcarry /* overflow? */
|
|
|
|
|
|
|
|
|
|
.Lctrcarrydone:
|
2018-09-10 17:41:13 +03:00
|
|
|
subs w4, w4, #1
|
2017-01-29 02:25:34 +03:00
|
|
|
bmi .Lctrtailblock /* blocks <0 means tail block */
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v3.16b}, [x1], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v3.16b, v0.16b, v3.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v3.16b}, [x0], #16
|
2017-01-17 16:46:29 +03:00
|
|
|
bne .Lctrloop
|
|
|
|
|
|
|
|
|
|
.Lctrout:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
st1 {vctr.16b}, [x5] /* return next CTR value */
|
2018-09-10 17:41:13 +03:00
|
|
|
ldp x29, x30, [sp], #16
|
2017-01-17 16:46:29 +03:00
|
|
|
ret
|
|
|
|
|
|
2017-01-29 02:25:34 +03:00
|
|
|
.Lctrtailblock:
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b}, [x0]
|
2019-02-14 11:03:54 +03:00
|
|
|
b .Lctrout
|
2017-01-17 16:46:29 +03:00
|
|
|
|
|
|
|
|
.Lctrcarry:
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
umov x7, vctr.d[0] /* load upper word of ctr */
|
2017-01-17 16:46:29 +03:00
|
|
|
rev x7, x7 /* ... to handle the carry */
|
|
|
|
|
add x7, x7, #1
|
|
|
|
|
rev x7, x7
|
crypto: arm64/aes-ce - implement 5 way interleave for ECB, CBC and CTR
This implements 5-way interleaving for ECB, CBC decryption and CTR,
resulting in a speedup of ~11% on Marvell ThunderX2, which has a
very deep pipeline and therefore a high issue latency for NEON
instructions operating on the same registers.
Note that XTS is left alone: implementing 5-way interleave there
would either involve spilling of the calculated tweaks to the
stack, or recalculating them after the encryption operation, and
doing either of those would most likely penalize low end cores.
For ECB, this is not a concern at all, given that we have plenty
of spare registers. For CTR and CBC decryption, we take advantage
of the fact that v16 is not used by the CE version of the code
(which is the only one targeted by the optimization), and so we
can reshuffle the code a bit and avoid having to spill to memory
(with the exception of one extra reload in the CBC routine)
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-06-24 20:38:31 +03:00
|
|
|
ins vctr.d[0], x7
|
2017-01-17 16:46:29 +03:00
|
|
|
b .Lctrcarrydone
|
2014-03-21 13:19:17 +04:00
|
|
|
AES_ENDPROC(aes_ctr_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* aes_xts_decrypt(u8 out[], u8 const in[], u8 const rk1[], int rounds,
|
|
|
|
|
* int blocks, u8 const rk2[], u8 iv[], int first)
|
|
|
|
|
* aes_xts_decrypt(u8 out[], u8 const in[], u8 const rk1[], int rounds,
|
|
|
|
|
* int blocks, u8 const rk2[], u8 iv[], int first)
|
|
|
|
|
*/
|
|
|
|
|
|
2018-09-10 17:41:15 +03:00
|
|
|
.macro next_tweak, out, in, tmp
|
2014-03-21 13:19:17 +04:00
|
|
|
sshr \tmp\().2d, \in\().2d, #63
|
2018-09-10 17:41:15 +03:00
|
|
|
and \tmp\().16b, \tmp\().16b, xtsmask.16b
|
2014-03-21 13:19:17 +04:00
|
|
|
add \out\().2d, \in\().2d, \in\().2d
|
|
|
|
|
ext \tmp\().16b, \tmp\().16b, \tmp\().16b, #8
|
|
|
|
|
eor \out\().16b, \out\().16b, \tmp\().16b
|
|
|
|
|
.endm
|
|
|
|
|
|
2018-09-10 17:41:15 +03:00
|
|
|
.macro xts_load_mask, tmp
|
|
|
|
|
movi xtsmask.2s, #0x1
|
|
|
|
|
movi \tmp\().2s, #0x87
|
|
|
|
|
uzp1 xtsmask.4s, xtsmask.4s, \tmp\().4s
|
|
|
|
|
.endm
|
2014-03-21 13:19:17 +04:00
|
|
|
|
|
|
|
|
AES_ENTRY(aes_xts_encrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
2018-03-10 18:21:51 +03:00
|
|
|
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v4.16b}, [x6]
|
2018-10-08 14:16:59 +03:00
|
|
|
xts_load_mask v8
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
cbz w7, .Lxtsencnotfirst
|
|
|
|
|
|
|
|
|
|
enc_prepare w3, x5, x8
|
|
|
|
|
encrypt_block v4, w3, x5, x8, w7 /* first tweak */
|
|
|
|
|
enc_switch_key w3, x2, x8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LxtsencNx
|
|
|
|
|
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
.Lxtsencnotfirst:
|
2018-09-10 17:41:13 +03:00
|
|
|
enc_prepare w3, x2, x8
|
2014-03-21 13:19:17 +04:00
|
|
|
.LxtsencloopNx:
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v4, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
.LxtsencNx:
|
2018-09-10 17:41:13 +03:00
|
|
|
subs w4, w4, #4
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lxtsenc1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 pt blocks */
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v5, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v6, v5, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v7, v6, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v3.16b, v3.16b, v7.16b
|
2018-03-10 18:21:51 +03:00
|
|
|
bl aes_encrypt_block4x
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v3.16b, v3.16b, v7.16b
|
|
|
|
|
eor v0.16b, v0.16b, v4.16b
|
|
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
2014-03-21 13:19:17 +04:00
|
|
|
mov v4.16b, v7.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
cbz w4, .Lxtsencout
|
2018-10-08 14:16:59 +03:00
|
|
|
xts_reload_mask v8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LxtsencloopNx
|
|
|
|
|
.Lxtsenc1x:
|
2018-09-10 17:41:13 +03:00
|
|
|
adds w4, w4, #4
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lxtsencout
|
|
|
|
|
.Lxtsencloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v1.16b}, [x1], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v1.16b, v4.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
encrypt_block v0, w3, x2, x8, w7
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lxtsencout
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v4, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .Lxtsencloop
|
|
|
|
|
.Lxtsencout:
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v4.16b}, [x6]
|
|
|
|
|
ldp x29, x30, [sp], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_xts_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_xts_decrypt)
|
2018-09-10 17:41:13 +03:00
|
|
|
stp x29, x30, [sp, #-16]!
|
|
|
|
|
mov x29, sp
|
2018-03-10 18:21:51 +03:00
|
|
|
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v4.16b}, [x6]
|
2018-10-08 14:16:59 +03:00
|
|
|
xts_load_mask v8
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
cbz w7, .Lxtsdecnotfirst
|
|
|
|
|
|
|
|
|
|
enc_prepare w3, x5, x8
|
|
|
|
|
encrypt_block v4, w3, x5, x8, w7 /* first tweak */
|
|
|
|
|
dec_prepare w3, x2, x8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LxtsdecNx
|
|
|
|
|
|
crypto: arm64/aes-blk - move kernel mode neon en/disable into loop
When kernel mode NEON was first introduced on arm64, the preserve and
restore of the userland NEON state was completely unoptimized, and
involved saving all registers on each call to kernel_neon_begin(),
and restoring them on each call to kernel_neon_end(). For this reason,
the NEON crypto code that was introduced at the time keeps the NEON
enabled throughout the execution of the crypto API methods, which may
include calls back into the crypto API that could result in memory
allocation or other actions that we should avoid when running with
preemption disabled.
Since then, we have optimized the kernel mode NEON handling, which now
restores lazily (upon return to userland), and so the preserve action
is only costly the first time it is called after entering the kernel.
So let's put the kernel_neon_begin() and kernel_neon_end() calls around
the actual invocations of the NEON crypto code, and run the remainder of
the code with kernel mode NEON disabled (and preemption enabled)
Note that this requires some reshuffling of the registers in the asm
code, because the XTS routines can no longer rely on the registers to
retain their contents between invocations.
Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2018-03-10 18:21:48 +03:00
|
|
|
.Lxtsdecnotfirst:
|
2018-09-10 17:41:13 +03:00
|
|
|
dec_prepare w3, x2, x8
|
2014-03-21 13:19:17 +04:00
|
|
|
.LxtsdecloopNx:
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v4, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
.LxtsdecNx:
|
2018-09-10 17:41:13 +03:00
|
|
|
subs w4, w4, #4
|
2014-03-21 13:19:17 +04:00
|
|
|
bmi .Lxtsdec1x
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v0.16b-v3.16b}, [x1], #64 /* get 4 ct blocks */
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v5, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v6, v5, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v7, v6, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v3.16b, v3.16b, v7.16b
|
2018-03-10 18:21:51 +03:00
|
|
|
bl aes_decrypt_block4x
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v3.16b, v3.16b, v7.16b
|
|
|
|
|
eor v0.16b, v0.16b, v4.16b
|
|
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b-v3.16b}, [x0], #64
|
2014-03-21 13:19:17 +04:00
|
|
|
mov v4.16b, v7.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
cbz w4, .Lxtsdecout
|
2018-10-08 14:16:59 +03:00
|
|
|
xts_reload_mask v8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .LxtsdecloopNx
|
|
|
|
|
.Lxtsdec1x:
|
2018-09-10 17:41:13 +03:00
|
|
|
adds w4, w4, #4
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lxtsdecout
|
|
|
|
|
.Lxtsdecloop:
|
2018-09-10 17:41:13 +03:00
|
|
|
ld1 {v1.16b}, [x1], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v1.16b, v4.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
decrypt_block v0, w3, x2, x8, w7
|
2014-03-21 13:19:17 +04:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v0.16b}, [x0], #16
|
|
|
|
|
subs w4, w4, #1
|
2014-03-21 13:19:17 +04:00
|
|
|
beq .Lxtsdecout
|
2018-09-10 17:41:15 +03:00
|
|
|
next_tweak v4, v4, v8
|
2014-03-21 13:19:17 +04:00
|
|
|
b .Lxtsdecloop
|
|
|
|
|
.Lxtsdecout:
|
2018-09-10 17:41:13 +03:00
|
|
|
st1 {v4.16b}, [x6]
|
|
|
|
|
ldp x29, x30, [sp], #16
|
2014-03-21 13:19:17 +04:00
|
|
|
ret
|
|
|
|
|
AES_ENDPROC(aes_xts_decrypt)
|
2017-02-03 17:49:37 +03:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* aes_mac_update(u8 const in[], u32 const rk[], int rounds,
|
|
|
|
|
* int blocks, u8 dg[], int enc_before, int enc_after)
|
|
|
|
|
*/
|
|
|
|
|
AES_ENTRY(aes_mac_update)
|
2018-04-30 19:18:24 +03:00
|
|
|
frame_push 6
|
|
|
|
|
|
|
|
|
|
mov x19, x0
|
|
|
|
|
mov x20, x1
|
|
|
|
|
mov x21, x2
|
|
|
|
|
mov x22, x3
|
|
|
|
|
mov x23, x4
|
|
|
|
|
mov x24, x6
|
|
|
|
|
|
|
|
|
|
ld1 {v0.16b}, [x23] /* get dg */
|
2017-02-03 17:49:37 +03:00
|
|
|
enc_prepare w2, x1, x7
|
2018-03-10 18:21:53 +03:00
|
|
|
cbz w5, .Lmacloop4x
|
2017-02-03 17:49:37 +03:00
|
|
|
|
2018-03-10 18:21:53 +03:00
|
|
|
encrypt_block v0, w2, x1, x7, w8
|
|
|
|
|
|
|
|
|
|
.Lmacloop4x:
|
2018-04-30 19:18:24 +03:00
|
|
|
subs w22, w22, #4
|
2018-03-10 18:21:53 +03:00
|
|
|
bmi .Lmac1x
|
2018-04-30 19:18:24 +03:00
|
|
|
ld1 {v1.16b-v4.16b}, [x19], #64 /* get next pt block */
|
2018-03-10 18:21:53 +03:00
|
|
|
eor v0.16b, v0.16b, v1.16b /* ..and xor with dg */
|
2018-04-30 19:18:24 +03:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 18:21:53 +03:00
|
|
|
eor v0.16b, v0.16b, v2.16b
|
2018-04-30 19:18:24 +03:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 18:21:53 +03:00
|
|
|
eor v0.16b, v0.16b, v3.16b
|
2018-04-30 19:18:24 +03:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 18:21:53 +03:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-04-30 19:18:24 +03:00
|
|
|
cmp w22, wzr
|
|
|
|
|
csinv x5, x24, xzr, eq
|
2018-03-10 18:21:53 +03:00
|
|
|
cbz w5, .Lmacout
|
2018-04-30 19:18:24 +03:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
|
|
|
|
st1 {v0.16b}, [x23] /* return dg */
|
|
|
|
|
cond_yield_neon .Lmacrestart
|
2018-03-10 18:21:53 +03:00
|
|
|
b .Lmacloop4x
|
|
|
|
|
.Lmac1x:
|
2018-04-30 19:18:24 +03:00
|
|
|
add w22, w22, #4
|
2017-02-03 17:49:37 +03:00
|
|
|
.Lmacloop:
|
2018-04-30 19:18:24 +03:00
|
|
|
cbz w22, .Lmacout
|
|
|
|
|
ld1 {v1.16b}, [x19], #16 /* get next pt block */
|
2017-02-03 17:49:37 +03:00
|
|
|
eor v0.16b, v0.16b, v1.16b /* ..and xor with dg */
|
|
|
|
|
|
2018-04-30 19:18:24 +03:00
|
|
|
subs w22, w22, #1
|
|
|
|
|
csinv x5, x24, xzr, eq
|
2017-02-03 17:49:37 +03:00
|
|
|
cbz w5, .Lmacout
|
|
|
|
|
|
2018-04-30 19:18:24 +03:00
|
|
|
.Lmacenc:
|
|
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2017-02-03 17:49:37 +03:00
|
|
|
b .Lmacloop
|
|
|
|
|
|
|
|
|
|
.Lmacout:
|
2018-04-30 19:18:24 +03:00
|
|
|
st1 {v0.16b}, [x23] /* return dg */
|
|
|
|
|
frame_pop
|
2017-02-03 17:49:37 +03:00
|
|
|
ret
|
2018-04-30 19:18:24 +03:00
|
|
|
|
|
|
|
|
.Lmacrestart:
|
|
|
|
|
ld1 {v0.16b}, [x23] /* get dg */
|
|
|
|
|
enc_prepare w21, x20, x0
|
|
|
|
|
b .Lmacloop4x
|
2017-02-03 17:49:37 +03:00
|
|
|
AES_ENDPROC(aes_mac_update)
|
