Linux cryptographic layer development
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Uros Bizjak <ubizjak@gmail.com>, Andy Polyakov <appro@cryptogams.org>
Cc: linux-crypto@vger.kernel.org, x86@kernel.org,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] crypto/x86: Use XORL r32,32 in poly1305-x86_64-cryptogams.pl
Date: Tue, 1 Sep 2020 21:16:11 +0200	[thread overview]
Message-ID: <20200901191611.GA869399@zx2c4.com> (raw)
In-Reply-To: <20200827173831.95039-1-ubizjak@gmail.com>

Hi Uros,

Any benchmarks for this? Seems like it's all in initialization code,
right? I'm CC'ing Andy into this.

Jason

On Thu, Aug 27, 2020 at 07:38:31PM +0200, Uros Bizjak wrote:
> x86_64 zero extends 32bit operations, so for 64bit operands,
> XORL r32,r32 is functionally equal to XORQ r64,r64, but avoids
> a REX prefix byte when legacy registers are used.
> 
> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
> Cc: Herbert Xu <herbert@gondor.apana.org.au>
> Cc: "David S. Miller" <davem@davemloft.net>
> ---
>  arch/x86/crypto/poly1305-x86_64-cryptogams.pl | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/arch/x86/crypto/poly1305-x86_64-cryptogams.pl b/arch/x86/crypto/poly1305-x86_64-cryptogams.pl
> index 137edcf038cb..7d568012cc15 100644
> --- a/arch/x86/crypto/poly1305-x86_64-cryptogams.pl
> +++ b/arch/x86/crypto/poly1305-x86_64-cryptogams.pl
> @@ -246,7 +246,7 @@ $code.=<<___ if (!$kernel);
>  ___
>  &declare_function("poly1305_init_x86_64", 32, 3);
>  $code.=<<___;
> -	xor	%rax,%rax
> +	xor	%eax,%eax
>  	mov	%rax,0($ctx)		# initialize hash value
>  	mov	%rax,8($ctx)
>  	mov	%rax,16($ctx)
> @@ -2853,7 +2853,7 @@ $code.=<<___;
>  .type	poly1305_init_base2_44,\@function,3
>  .align	32
>  poly1305_init_base2_44:
> -	xor	%rax,%rax
> +	xor	%eax,%eax
>  	mov	%rax,0($ctx)		# initialize hash value
>  	mov	%rax,8($ctx)
>  	mov	%rax,16($ctx)
> @@ -3947,7 +3947,7 @@ xor128_decrypt_n_pad:
>  	mov	\$16,$len
>  	sub	%r10,$len
>  	xor	%eax,%eax
> -	xor	%r11,%r11
> +	xor	%r11d,%r11d
>  .Loop_dec_byte:
>  	mov	($inp,$otp),%r11b
>  	mov	($otp),%al
> @@ -4085,7 +4085,7 @@ avx_handler:
>  	.long	0xa548f3fc		# cld; rep movsq
>  
>  	mov	$disp,%rsi
> -	xor	%rcx,%rcx		# arg1, UNW_FLAG_NHANDLER
> +	xor	%ecx,%ecx		# arg1, UNW_FLAG_NHANDLER
>  	mov	8(%rsi),%rdx		# arg2, disp->ImageBase
>  	mov	0(%rsi),%r8		# arg3, disp->ControlPc
>  	mov	16(%rsi),%r9		# arg4, disp->FunctionEntry
> -- 
> 2.26.2
> 

-- 
Jason A. Donenfeld
Deep Space Explorer
fr: +33 6 51 90 82 66
us: +1 513 476 1200
www.jasondonenfeld.com
www.zx2c4.com
zx2c4.com/keys/AB9942E6D4A4CFC3412620A749FC7012A5DE03AE.asc

  reply	other threads:[~2020-09-01 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27 17:38 [PATCH] crypto/x86: Use XORL r32,32 in poly1305-x86_64-cryptogams.pl Uros Bizjak
2020-09-01 19:16 ` Jason A. Donenfeld [this message]
2020-09-02  5:52   ` Uros Bizjak
2020-09-07 13:16 ` Jason A. Donenfeld
2020-09-11  6:56 ` Herbert Xu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200901191611.GA869399@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=appro@cryptogams.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=ubizjak@gmail.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox