2014-03-21 17:19:17 +08:00
|
|
|
/*
|
|
|
|
* linux/arch/arm64/crypto/aes-modes.S - chaining mode wrappers for AES
|
|
|
|
*
|
2017-02-03 22:49:37 +08:00
|
|
|
* Copyright (C) 2013 - 2017 Linaro Ltd <ard.biesheuvel@linaro.org>
|
2014-03-21 17:19:17 +08:00
|
|
|
*
|
|
|
|
* This program is free software; you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License version 2 as
|
|
|
|
* published by the Free Software Foundation.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* included by aes-ce.S and aes-neon.S */
|
|
|
|
|
|
|
|
.text
|
|
|
|
.align 4
|
|
|
|
|
|
|
|
aes_encrypt_block4x:
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block4x v0, v1, v2, v3, w22, x21, x8, w7
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
ENDPROC(aes_encrypt_block4x)
|
|
|
|
|
|
|
|
aes_decrypt_block4x:
|
2018-05-01 00:18:24 +08:00
|
|
|
decrypt_block4x v0, v1, v2, v3, w22, x21, x8, w7
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
ENDPROC(aes_decrypt_block4x)
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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 23:21:48 +08:00
|
|
|
* int blocks)
|
2014-03-21 17:19:17 +08: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 23:21:48 +08:00
|
|
|
* int blocks)
|
2014-03-21 17:19:17 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ecb_encrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 5
|
2014-03-21 17:19:17 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
|
|
|
|
.Lecbencrestart:
|
|
|
|
enc_prepare w22, x21, x5
|
2014-03-21 17:19:17 +08:00
|
|
|
|
|
|
|
.LecbencloopNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lecbenc1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 pt blocks */
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_encrypt_block4x
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
|
|
|
cond_yield_neon .Lecbencrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LecbencloopNx
|
|
|
|
.Lecbenc1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lecbencout
|
|
|
|
.Lecbencloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b}, [x20], #16 /* get next pt block */
|
|
|
|
encrypt_block v0, w22, x21, x5, w6
|
|
|
|
st1 {v0.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
bne .Lecbencloop
|
|
|
|
.Lecbencout:
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
AES_ENDPROC(aes_ecb_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ecb_decrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 5
|
|
|
|
|
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
2014-03-21 17:19:17 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
.Lecbdecrestart:
|
|
|
|
dec_prepare w22, x21, x5
|
2014-03-21 17:19:17 +08:00
|
|
|
|
|
|
|
.LecbdecloopNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lecbdec1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 ct blocks */
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_decrypt_block4x
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
|
|
|
cond_yield_neon .Lecbdecrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LecbdecloopNx
|
|
|
|
.Lecbdec1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lecbdecout
|
|
|
|
.Lecbdecloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b}, [x20], #16 /* get next ct block */
|
|
|
|
decrypt_block v0, w22, x21, x5, w6
|
|
|
|
st1 {v0.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
bne .Lecbdecloop
|
|
|
|
.Lecbdecout:
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08: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 23:21:48 +08:00
|
|
|
* int blocks, u8 iv[])
|
2014-03-21 17:19:17 +08: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 23:21:48 +08:00
|
|
|
* int blocks, u8 iv[])
|
2014-03-21 17:19:17 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_encrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 6
|
|
|
|
|
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
mov x24, x5
|
|
|
|
|
|
|
|
.Lcbcencrestart:
|
|
|
|
ld1 {v4.16b}, [x24] /* get iv */
|
|
|
|
enc_prepare w22, x21, x6
|
2014-03-21 17:19:17 +08:00
|
|
|
|
2018-03-10 23:21:52 +08:00
|
|
|
.Lcbcencloop4x:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2018-03-10 23:21:52 +08:00
|
|
|
bmi .Lcbcenc1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 pt blocks */
|
2018-03-10 23:21:52 +08:00
|
|
|
eor v0.16b, v0.16b, v4.16b /* ..and xor with iv */
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w22, x21, x6, w7
|
2018-03-10 23:21:52 +08:00
|
|
|
eor v1.16b, v1.16b, v0.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v1, w22, x21, x6, w7
|
2018-03-10 23:21:52 +08:00
|
|
|
eor v2.16b, v2.16b, v1.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v2, w22, x21, x6, w7
|
2018-03-10 23:21:52 +08:00
|
|
|
eor v3.16b, v3.16b, v2.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v3, w22, x21, x6, w7
|
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
2018-03-10 23:21:52 +08:00
|
|
|
mov v4.16b, v3.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v4.16b}, [x24] /* return iv */
|
|
|
|
cond_yield_neon .Lcbcencrestart
|
2018-03-10 23:21:52 +08:00
|
|
|
b .Lcbcencloop4x
|
|
|
|
.Lcbcenc1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2018-03-10 23:21:52 +08:00
|
|
|
beq .Lcbcencout
|
|
|
|
.Lcbcencloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b}, [x20], #16 /* get next pt block */
|
2018-03-10 23:21:52 +08:00
|
|
|
eor v4.16b, v4.16b, v0.16b /* ..and xor with iv */
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v4, w22, x21, x6, w7
|
|
|
|
st1 {v4.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
bne .Lcbcencloop
|
2018-03-10 23:21:52 +08:00
|
|
|
.Lcbcencout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v4.16b}, [x24] /* return iv */
|
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
AES_ENDPROC(aes_cbc_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_cbc_decrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 6
|
|
|
|
|
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
mov x24, x5
|
2014-03-21 17:19:17 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
.Lcbcdecrestart:
|
|
|
|
ld1 {v7.16b}, [x24] /* get iv */
|
|
|
|
dec_prepare w22, x21, x6
|
2014-03-21 17:19:17 +08:00
|
|
|
|
|
|
|
.LcbcdecloopNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lcbcdec1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 ct blocks */
|
2014-03-21 17:19:17 +08:00
|
|
|
mov v4.16b, v0.16b
|
|
|
|
mov v5.16b, v1.16b
|
|
|
|
mov v6.16b, v2.16b
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_decrypt_block4x
|
2018-05-01 00:18:24 +08:00
|
|
|
sub x20, x20, #16
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v0.16b, v7.16b
|
|
|
|
eor v1.16b, v1.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v7.16b}, [x20], #16 /* reload 1 ct block */
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v2.16b, v2.16b, v5.16b
|
|
|
|
eor v3.16b, v3.16b, v6.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
|
|
|
st1 {v7.16b}, [x24] /* return iv */
|
|
|
|
cond_yield_neon .Lcbcdecrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LcbcdecloopNx
|
|
|
|
.Lcbcdec1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lcbcdecout
|
|
|
|
.Lcbcdecloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v1.16b}, [x20], #16 /* get next ct block */
|
2014-03-21 17:19:17 +08:00
|
|
|
mov v0.16b, v1.16b /* ...and copy to v0 */
|
2018-05-01 00:18:24 +08:00
|
|
|
decrypt_block v0, w22, x21, x6, w7
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v0.16b, v7.16b /* xor with iv => pt */
|
|
|
|
mov v7.16b, v1.16b /* ct is next iv */
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
bne .Lcbcdecloop
|
|
|
|
.Lcbcdecout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v7.16b}, [x24] /* return iv */
|
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
AES_ENDPROC(aes_cbc_decrypt)
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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 23:21:48 +08:00
|
|
|
* int blocks, u8 ctr[])
|
2014-03-21 17:19:17 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
AES_ENTRY(aes_ctr_encrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 6
|
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 23:21:48 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
mov x24, x5
|
|
|
|
|
|
|
|
.Lctrrestart:
|
|
|
|
enc_prepare w22, x21, x6
|
|
|
|
ld1 {v4.16b}, [x24]
|
2017-01-17 21:46:29 +08: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 23:21:48 +08:00
|
|
|
umov x6, v4.d[1] /* keep swabbed ctr in reg */
|
|
|
|
rev x6, x6
|
2014-03-21 17:19:17 +08:00
|
|
|
.LctrloopNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lctr1x
|
2018-05-01 00:18:24 +08:00
|
|
|
cmn w6, #4 /* 32 bit overflow? */
|
|
|
|
bcs .Lctr1x
|
2014-03-21 17:19:17 +08:00
|
|
|
ldr q8, =0x30000000200000001 /* addends 1,2,3[,0] */
|
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 23:21:48 +08:00
|
|
|
dup v7.4s, w6
|
2014-03-21 17:19:17 +08:00
|
|
|
mov v0.16b, v4.16b
|
|
|
|
add v7.4s, v7.4s, v8.4s
|
|
|
|
mov v1.16b, v4.16b
|
|
|
|
rev32 v8.16b, v7.16b
|
|
|
|
mov v2.16b, v4.16b
|
|
|
|
mov v3.16b, v4.16b
|
|
|
|
mov v1.s[3], v8.s[0]
|
|
|
|
mov v2.s[3], v8.s[1]
|
|
|
|
mov v3.s[3], v8.s[2]
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v5.16b-v7.16b}, [x20], #48 /* get 3 input blocks */
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_encrypt_block4x
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v5.16b, v0.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v5.16b}, [x20], #16 /* get 1 input block */
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v1.16b, v6.16b, v1.16b
|
|
|
|
eor v2.16b, v7.16b, v2.16b
|
|
|
|
eor v3.16b, v5.16b, v3.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
2018-03-10 23:21:51 +08:00
|
|
|
add x6, x6, #4
|
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 23:21:48 +08:00
|
|
|
rev x7, x6
|
2014-03-21 17:19:17 +08:00
|
|
|
ins v4.d[1], x7
|
2018-05-01 00:18:24 +08:00
|
|
|
cbz w23, .Lctrout
|
|
|
|
st1 {v4.16b}, [x24] /* return next CTR value */
|
|
|
|
cond_yield_neon .Lctrrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LctrloopNx
|
|
|
|
.Lctr1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lctrout
|
|
|
|
.Lctrloop:
|
|
|
|
mov v0.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w22, x21, x8, w7
|
2017-01-17 21:46:29 +08: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 23:21:48 +08:00
|
|
|
adds x6, x6, #1 /* increment BE ctr */
|
|
|
|
rev x7, x6
|
2017-01-17 21:46:29 +08:00
|
|
|
ins v4.d[1], x7
|
|
|
|
bcs .Lctrcarry /* overflow? */
|
|
|
|
|
|
|
|
.Lctrcarrydone:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #1
|
2017-01-29 07:25:34 +08:00
|
|
|
bmi .Lctrtailblock /* blocks <0 means tail block */
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v3.16b}, [x20], #16
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v3.16b, v0.16b, v3.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v3.16b}, [x19], #16
|
2017-01-17 21:46:29 +08:00
|
|
|
bne .Lctrloop
|
|
|
|
|
|
|
|
.Lctrout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v4.16b}, [x24] /* return next CTR value */
|
|
|
|
.Lctrret:
|
|
|
|
frame_pop
|
2017-01-17 21:46:29 +08:00
|
|
|
ret
|
|
|
|
|
2017-01-29 07:25:34 +08:00
|
|
|
.Lctrtailblock:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b}, [x19]
|
|
|
|
b .Lctrret
|
2017-01-17 21:46:29 +08:00
|
|
|
|
|
|
|
.Lctrcarry:
|
|
|
|
umov x7, v4.d[0] /* load upper word of ctr */
|
|
|
|
rev x7, x7 /* ... to handle the carry */
|
|
|
|
add x7, x7, #1
|
|
|
|
rev x7, x7
|
|
|
|
ins v4.d[0], x7
|
|
|
|
b .Lctrcarrydone
|
2014-03-21 17:19:17 +08:00
|
|
|
AES_ENDPROC(aes_ctr_encrypt)
|
|
|
|
.ltorg
|
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
* 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)
|
|
|
|
*/
|
|
|
|
|
|
|
|
.macro next_tweak, out, in, const, tmp
|
|
|
|
sshr \tmp\().2d, \in\().2d, #63
|
|
|
|
and \tmp\().16b, \tmp\().16b, \const\().16b
|
|
|
|
add \out\().2d, \in\().2d, \in\().2d
|
|
|
|
ext \tmp\().16b, \tmp\().16b, \tmp\().16b, #8
|
|
|
|
eor \out\().16b, \out\().16b, \tmp\().16b
|
|
|
|
.endm
|
|
|
|
|
|
|
|
.Lxts_mul_x:
|
2016-10-12 02:15:19 +08:00
|
|
|
CPU_LE( .quad 1, 0x87 )
|
|
|
|
CPU_BE( .quad 0x87, 1 )
|
2014-03-21 17:19:17 +08:00
|
|
|
|
|
|
|
AES_ENTRY(aes_xts_encrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 6
|
|
|
|
|
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
mov x24, x6
|
2018-03-10 23:21:51 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v4.16b}, [x24]
|
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 23:21:48 +08: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 17:19:17 +08:00
|
|
|
ldr q7, .Lxts_mul_x
|
|
|
|
b .LxtsencNx
|
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
.Lxtsencrestart:
|
|
|
|
ld1 {v4.16b}, [x24]
|
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 23:21:48 +08:00
|
|
|
.Lxtsencnotfirst:
|
2018-05-01 00:18:24 +08:00
|
|
|
enc_prepare w22, x21, x8
|
2014-03-21 17:19:17 +08:00
|
|
|
.LxtsencloopNx:
|
|
|
|
ldr q7, .Lxts_mul_x
|
|
|
|
next_tweak v4, v4, v7, v8
|
|
|
|
.LxtsencNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lxtsenc1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 pt blocks */
|
2014-03-21 17:19:17 +08:00
|
|
|
next_tweak v5, v4, v7, v8
|
|
|
|
eor v0.16b, v0.16b, v4.16b
|
|
|
|
next_tweak v6, v5, v7, v8
|
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
|
|
|
next_tweak v7, v6, v7, v8
|
|
|
|
eor v3.16b, v3.16b, v7.16b
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_encrypt_block4x
|
2014-03-21 17:19:17 +08: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-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
2014-03-21 17:19:17 +08:00
|
|
|
mov v4.16b, v7.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
cbz w23, .Lxtsencout
|
|
|
|
st1 {v4.16b}, [x24]
|
|
|
|
cond_yield_neon .Lxtsencrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LxtsencloopNx
|
|
|
|
.Lxtsenc1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lxtsencout
|
|
|
|
.Lxtsencloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v1.16b}, [x20], #16
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v1.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w22, x21, x8, w7
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lxtsencout
|
|
|
|
next_tweak v4, v4, v7, v8
|
|
|
|
b .Lxtsencloop
|
|
|
|
.Lxtsencout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v4.16b}, [x24]
|
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
AES_ENDPROC(aes_xts_encrypt)
|
|
|
|
|
|
|
|
|
|
|
|
AES_ENTRY(aes_xts_decrypt)
|
2018-05-01 00:18:24 +08:00
|
|
|
frame_push 6
|
2018-03-10 23:21:51 +08:00
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
mov x19, x0
|
|
|
|
mov x20, x1
|
|
|
|
mov x21, x2
|
|
|
|
mov x22, x3
|
|
|
|
mov x23, x4
|
|
|
|
mov x24, x6
|
|
|
|
|
|
|
|
ld1 {v4.16b}, [x24]
|
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 23:21:48 +08: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 17:19:17 +08:00
|
|
|
ldr q7, .Lxts_mul_x
|
|
|
|
b .LxtsdecNx
|
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
.Lxtsdecrestart:
|
|
|
|
ld1 {v4.16b}, [x24]
|
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 23:21:48 +08:00
|
|
|
.Lxtsdecnotfirst:
|
2018-05-01 00:18:24 +08:00
|
|
|
dec_prepare w22, x21, x8
|
2014-03-21 17:19:17 +08:00
|
|
|
.LxtsdecloopNx:
|
|
|
|
ldr q7, .Lxts_mul_x
|
|
|
|
next_tweak v4, v4, v7, v8
|
|
|
|
.LxtsdecNx:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
bmi .Lxtsdec1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v0.16b-v3.16b}, [x20], #64 /* get 4 ct blocks */
|
2014-03-21 17:19:17 +08:00
|
|
|
next_tweak v5, v4, v7, v8
|
|
|
|
eor v0.16b, v0.16b, v4.16b
|
|
|
|
next_tweak v6, v5, v7, v8
|
|
|
|
eor v1.16b, v1.16b, v5.16b
|
|
|
|
eor v2.16b, v2.16b, v6.16b
|
|
|
|
next_tweak v7, v6, v7, v8
|
|
|
|
eor v3.16b, v3.16b, v7.16b
|
2018-03-10 23:21:51 +08:00
|
|
|
bl aes_decrypt_block4x
|
2014-03-21 17:19:17 +08: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-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b-v3.16b}, [x19], #64
|
2014-03-21 17:19:17 +08:00
|
|
|
mov v4.16b, v7.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
cbz w23, .Lxtsdecout
|
|
|
|
st1 {v4.16b}, [x24]
|
|
|
|
cond_yield_neon .Lxtsdecrestart
|
2014-03-21 17:19:17 +08:00
|
|
|
b .LxtsdecloopNx
|
|
|
|
.Lxtsdec1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
adds w23, w23, #4
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lxtsdecout
|
|
|
|
.Lxtsdecloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v1.16b}, [x20], #16
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v1.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
decrypt_block v0, w22, x21, x8, w7
|
2014-03-21 17:19:17 +08:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b}, [x19], #16
|
|
|
|
subs w23, w23, #1
|
2014-03-21 17:19:17 +08:00
|
|
|
beq .Lxtsdecout
|
|
|
|
next_tweak v4, v4, v7, v8
|
|
|
|
b .Lxtsdecloop
|
|
|
|
.Lxtsdecout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v4.16b}, [x24]
|
|
|
|
frame_pop
|
2014-03-21 17:19:17 +08:00
|
|
|
ret
|
|
|
|
AES_ENDPROC(aes_xts_decrypt)
|
2017-02-03 22:49:37 +08: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-05-01 00:18:24 +08: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 22:49:37 +08:00
|
|
|
enc_prepare w2, x1, x7
|
2018-03-10 23:21:53 +08:00
|
|
|
cbz w5, .Lmacloop4x
|
2017-02-03 22:49:37 +08:00
|
|
|
|
2018-03-10 23:21:53 +08:00
|
|
|
encrypt_block v0, w2, x1, x7, w8
|
|
|
|
|
|
|
|
.Lmacloop4x:
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w22, w22, #4
|
2018-03-10 23:21:53 +08:00
|
|
|
bmi .Lmac1x
|
2018-05-01 00:18:24 +08:00
|
|
|
ld1 {v1.16b-v4.16b}, [x19], #64 /* get next pt block */
|
2018-03-10 23:21:53 +08:00
|
|
|
eor v0.16b, v0.16b, v1.16b /* ..and xor with dg */
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 23:21:53 +08:00
|
|
|
eor v0.16b, v0.16b, v2.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 23:21:53 +08:00
|
|
|
eor v0.16b, v0.16b, v3.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2018-03-10 23:21:53 +08:00
|
|
|
eor v0.16b, v0.16b, v4.16b
|
2018-05-01 00:18:24 +08:00
|
|
|
cmp w22, wzr
|
|
|
|
csinv x5, x24, xzr, eq
|
2018-03-10 23:21:53 +08:00
|
|
|
cbz w5, .Lmacout
|
2018-05-01 00:18:24 +08:00
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
|
|
|
st1 {v0.16b}, [x23] /* return dg */
|
|
|
|
cond_yield_neon .Lmacrestart
|
2018-03-10 23:21:53 +08:00
|
|
|
b .Lmacloop4x
|
|
|
|
.Lmac1x:
|
2018-05-01 00:18:24 +08:00
|
|
|
add w22, w22, #4
|
2017-02-03 22:49:37 +08:00
|
|
|
.Lmacloop:
|
2018-05-01 00:18:24 +08:00
|
|
|
cbz w22, .Lmacout
|
|
|
|
ld1 {v1.16b}, [x19], #16 /* get next pt block */
|
2017-02-03 22:49:37 +08:00
|
|
|
eor v0.16b, v0.16b, v1.16b /* ..and xor with dg */
|
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
subs w22, w22, #1
|
|
|
|
csinv x5, x24, xzr, eq
|
2017-02-03 22:49:37 +08:00
|
|
|
cbz w5, .Lmacout
|
|
|
|
|
2018-05-01 00:18:24 +08:00
|
|
|
.Lmacenc:
|
|
|
|
encrypt_block v0, w21, x20, x7, w8
|
2017-02-03 22:49:37 +08:00
|
|
|
b .Lmacloop
|
|
|
|
|
|
|
|
.Lmacout:
|
2018-05-01 00:18:24 +08:00
|
|
|
st1 {v0.16b}, [x23] /* return dg */
|
|
|
|
frame_pop
|
2017-02-03 22:49:37 +08:00
|
|
|
ret
|
2018-05-01 00:18:24 +08:00
|
|
|
|
|
|
|
.Lmacrestart:
|
|
|
|
ld1 {v0.16b}, [x23] /* get dg */
|
|
|
|
enc_prepare w21, x20, x0
|
|
|
|
b .Lmacloop4x
|
2017-02-03 22:49:37 +08:00
|
|
|
AES_ENDPROC(aes_mac_update)
|