[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3d857119-8eb4-4dc0-8543-f30922d53187@linux.ibm.com>
Date: Wed, 15 May 2024 07:59:38 -0500
From: Danny Tsen <dtsen@...ux.ibm.com>
To: Andy Polyakov <appro@...ptogams.org>, linux-crypto@...r.kernel.org
Cc: herbert@...dor.apana.org.au, leitao@...ian.org, nayna@...ux.ibm.com,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
mpe@...erman.id.au, ltcgcw@...ux.vnet.ibm.com, dtsen@...ibm.com
Subject: Re: [PATCH 1/3] crypto: X25519 low-level primitives for ppc64le.
Thank you Andy. Will fix this.
On 5/15/24 3:11 AM, Andy Polyakov wrote:
> Hi,
>
> Couple of remarks inline.
>
>> +# [1] https://www.openssl.org/~appro/cryptogams/
>
> https://github.com/dot-asm/cryptogams/ is arguably better reference.
>
>> +SYM_FUNC_START(x25519_fe51_mul)
>> +.align 5
>
> The goal is to align the label, not the first instruction after the
> directive. It's not a problem in this spot, in the beginning of the
> module that is, but further below it's likely to inject redundant nops
> between the label and meaningful code. But since the directive in
> question is not position-sensitive one can resolve this by changing
> the order of the directive and the SYM_FUNC_START macro.
>
> Cheers.
>
Powered by blists - more mailing lists