All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
	ebiggers@kernel.org, linux-riscv@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	aou@eecs.berkeley.edu, christoph.muellner@vrull.eu,
	heiko.stuebner@vrull.eu
Subject: Re: [PATCH] crypto: riscv/aes - Implement scalar Zkn version for RV32
Date: Wed, 1 Nov 2023 11:10:28 +0100	[thread overview]
Message-ID: <CAMj1kXE7g9Xvn+SMRyJWJpC_Au3JguSMRj0p1cCF4azSMc6y2Q@mail.gmail.com> (raw)
In-Reply-To: <20231027-stage-cable-022844c2567d@spud>

On Fri, 27 Oct 2023 at 15:17, Conor Dooley <conor@kernel.org> wrote:
>
> On Fri, Oct 27, 2023 at 06:11:40AM -0700, Palmer Dabbelt wrote:
> > On Thu, 31 Aug 2023 10:10:21 PDT (-0700), Ard Biesheuvel wrote:
> > > On Fri, 4 Aug 2023 at 10:31, Ard Biesheuvel <ardb@kernel.org> wrote:
> > > >
> > > > On Fri, 4 Aug 2023 at 10:21, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > > > >
> > > ...
> > >
> > > > > Hi Ard:
> > > > >
> > > > > Any chance you could postpone this til after I've finished removing
> > > > > crypto_cipher?
> > > > >
> > > >
> > > > That's fine with me. Do you have an ETA on that? Need any help?
> > > >
> > > > I have implemented the scalar 64-bit counterpart as well in the mean time
> > >
> > > Is this still happening?
> >
> > I don't really know much about the crypto stuff, but looks like there's
> > still a "struct crypto_cipher" in my trees.  Am I still supposed to be
> > waiting on something?
>
> Regardless of crypto_cipher structs, this needs whatever series that
> actually implements Zkn detection from DT/ACPI to be merged first,
> as otherwise the definitions that iscv_isa_extension_available() depends
> on don't exist.
>

Please disregard this patch. I have an updated version already, but
I'll need to rebase it once the prerequisites are in place.

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=riscv-scalar-aes

WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ardb@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
	herbert@gondor.apana.org.au,  linux-crypto@vger.kernel.org,
	ebiggers@kernel.org,  linux-riscv@lists.infradead.org,
	Paul Walmsley <paul.walmsley@sifive.com>,
	 aou@eecs.berkeley.edu, christoph.muellner@vrull.eu,
	heiko.stuebner@vrull.eu
Subject: Re: [PATCH] crypto: riscv/aes - Implement scalar Zkn version for RV32
Date: Wed, 1 Nov 2023 11:10:28 +0100	[thread overview]
Message-ID: <CAMj1kXE7g9Xvn+SMRyJWJpC_Au3JguSMRj0p1cCF4azSMc6y2Q@mail.gmail.com> (raw)
In-Reply-To: <20231027-stage-cable-022844c2567d@spud>

On Fri, 27 Oct 2023 at 15:17, Conor Dooley <conor@kernel.org> wrote:
>
> On Fri, Oct 27, 2023 at 06:11:40AM -0700, Palmer Dabbelt wrote:
> > On Thu, 31 Aug 2023 10:10:21 PDT (-0700), Ard Biesheuvel wrote:
> > > On Fri, 4 Aug 2023 at 10:31, Ard Biesheuvel <ardb@kernel.org> wrote:
> > > >
> > > > On Fri, 4 Aug 2023 at 10:21, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > > > >
> > > ...
> > >
> > > > > Hi Ard:
> > > > >
> > > > > Any chance you could postpone this til after I've finished removing
> > > > > crypto_cipher?
> > > > >
> > > >
> > > > That's fine with me. Do you have an ETA on that? Need any help?
> > > >
> > > > I have implemented the scalar 64-bit counterpart as well in the mean time
> > >
> > > Is this still happening?
> >
> > I don't really know much about the crypto stuff, but looks like there's
> > still a "struct crypto_cipher" in my trees.  Am I still supposed to be
> > waiting on something?
>
> Regardless of crypto_cipher structs, this needs whatever series that
> actually implements Zkn detection from DT/ACPI to be merged first,
> as otherwise the definitions that iscv_isa_extension_available() depends
> on don't exist.
>

Please disregard this patch. I have an updated version already, but
I'll need to rebase it once the prerequisites are in place.

https://git.kernel.org/pub/scm/linux/kernel/git/ardb/linux.git/log/?h=riscv-scalar-aes

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2023-11-01 10:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 17:29 [PATCH] crypto: riscv/aes - Implement scalar Zkn version for RV32 Ard Biesheuvel
2023-07-26 17:29 ` Ard Biesheuvel
2023-08-04  8:21 ` Herbert Xu
2023-08-04  8:21   ` Herbert Xu
2023-08-04  8:31   ` Ard Biesheuvel
2023-08-04  8:31     ` Ard Biesheuvel
2023-08-31 17:10     ` Ard Biesheuvel
2023-08-31 17:10       ` Ard Biesheuvel
     [not found]       ` <mhng-ff1fe914-36e9-42e8-88ac-44c7f6976e3d@palmer-ri-x1c9>
2023-10-29 11:12         ` Herbert Xu
2023-10-29 11:12           ` Herbert Xu
     [not found]         ` <20231027-stage-cable-022844c2567d@spud>
2023-11-01 10:10           ` Ard Biesheuvel [this message]
2023-11-01 10:10             ` Ard Biesheuvel

Reply instructions:

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

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

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

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

  git send-email \
    --in-reply-to=CAMj1kXE7g9Xvn+SMRyJWJpC_Au3JguSMRj0p1cCF4azSMc6y2Q@mail.gmail.com \
    --to=ardb@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=christoph.muellner@vrull.eu \
    --cc=conor@kernel.org \
    --cc=ebiggers@kernel.org \
    --cc=heiko.stuebner@vrull.eu \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.