From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Harsha Harsha <harshah@xilinx.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Michal Simek <michals@xilinx.com>,
Sarat Chand Savitala <saratcha@xilinx.com>,
Harsh Jain <harshj@xilinx.com>, git <git@xilinx.com>
Subject: Re: [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality
Date: Tue, 22 Feb 2022 10:47:03 +0100 [thread overview]
Message-ID: <YhSxF5nDzwsY9BFS@Red> (raw)
In-Reply-To: <SJ0PR02MB7279894629DCA2758355A9D2DE3A9@SJ0PR02MB7279.namprd02.prod.outlook.com>
Le Mon, Feb 21, 2022 at 12:17:02PM +0000, Harsha Harsha a écrit :
>
>
> > -----Original Message-----
> > From: Corentin Labbe <clabbe.montjoie@gmail.com>
> > Sent: Friday, February 18, 2022 3:13 PM
> > To: Harsha Harsha <harshah@xilinx.com>
> > Cc: herbert@gondor.apana.org.au; davem@davemloft.net; linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> > kernel@lists.infradead.org; Michal Simek <michals@xilinx.com>; Sarat Chand Savitala <saratcha@xilinx.com>; Harsh Jain
> > <harshj@xilinx.com>; git <git@xilinx.com>
> > Subject: Re: [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality
> >
> > Le Fri, Feb 18, 2022 at 12:44:22AM +0530, Harsha a écrit :
> > > This patch adds zynqmp_pm_sha_hash API in the ZynqMP firmware to compute
> > > SHA3 hash of given data.
> > >
> > > Signed-off-by: Harsha <harsha.harsha@xilinx.com>
> > > Acked-by: Michal Simek <michal.simek@xilinx.com>
> > > ---
> >
> > Hello
> >
> > Your signed-off should contain your real name.
>
> My complete name is Harsha which I have mentioned in the signed-off section.
I am sorry, I believed it was your pseudo. If it is your real name, no change are needed.
>
> > Furthermore why did you drop copyright from previous poster ?
> > See https://patchwork.kernel.org/project/linux-crypto/cover/1556793282-17346-1-git-send-email-kalyani.akula@xilinx.com/ for
> > reference.
>
> I did not understand the comment. Do you want me to add Kalyani's name also in the Signed of section?
>
> >
> > Furthermore, the previous poster didnt answered my questions about parallel processing and tests.
>
> Since SHA3 HW engine in ZynqMPSoC does not support parallel processing of 2 hash requests, so we have changed our approach.
> Now to support parallel processing of 2 hash requests, software fallback is being used for init, update, final, export and import in the ZynqMP SHA driver.
> For digest, the calculation of SHA3 hash is done by the hardened SHA3 accelerator in Xilinx ZynqMP SoC.
>
I asked for parallel processing since I didnt see any locking or way to prevent hardware to be used in the same time.
But the final work is done by a firmware call, so my knowledge stop here.
> Following tests have been done for the driver:
> - Enabled kernel self tests and extra run-time crypto self tests
> - Tested SHA hash computation for different sizes of data using userspace application
> - Tested SHA hash computation using multiple updates of data using userspace application
> - Tested parallel hash computation
> - Tested using the tcrypt module
>
This should be in the cover letter.
Regards
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Harsha Harsha <harshah@xilinx.com>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Michal Simek <michals@xilinx.com>,
Sarat Chand Savitala <saratcha@xilinx.com>,
Harsh Jain <harshj@xilinx.com>, git <git@xilinx.com>
Subject: Re: [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality
Date: Tue, 22 Feb 2022 10:47:03 +0100 [thread overview]
Message-ID: <YhSxF5nDzwsY9BFS@Red> (raw)
In-Reply-To: <SJ0PR02MB7279894629DCA2758355A9D2DE3A9@SJ0PR02MB7279.namprd02.prod.outlook.com>
Le Mon, Feb 21, 2022 at 12:17:02PM +0000, Harsha Harsha a écrit :
>
>
> > -----Original Message-----
> > From: Corentin Labbe <clabbe.montjoie@gmail.com>
> > Sent: Friday, February 18, 2022 3:13 PM
> > To: Harsha Harsha <harshah@xilinx.com>
> > Cc: herbert@gondor.apana.org.au; davem@davemloft.net; linux-crypto@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> > kernel@lists.infradead.org; Michal Simek <michals@xilinx.com>; Sarat Chand Savitala <saratcha@xilinx.com>; Harsh Jain
> > <harshj@xilinx.com>; git <git@xilinx.com>
> > Subject: Re: [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality
> >
> > Le Fri, Feb 18, 2022 at 12:44:22AM +0530, Harsha a écrit :
> > > This patch adds zynqmp_pm_sha_hash API in the ZynqMP firmware to compute
> > > SHA3 hash of given data.
> > >
> > > Signed-off-by: Harsha <harsha.harsha@xilinx.com>
> > > Acked-by: Michal Simek <michal.simek@xilinx.com>
> > > ---
> >
> > Hello
> >
> > Your signed-off should contain your real name.
>
> My complete name is Harsha which I have mentioned in the signed-off section.
I am sorry, I believed it was your pseudo. If it is your real name, no change are needed.
>
> > Furthermore why did you drop copyright from previous poster ?
> > See https://patchwork.kernel.org/project/linux-crypto/cover/1556793282-17346-1-git-send-email-kalyani.akula@xilinx.com/ for
> > reference.
>
> I did not understand the comment. Do you want me to add Kalyani's name also in the Signed of section?
>
> >
> > Furthermore, the previous poster didnt answered my questions about parallel processing and tests.
>
> Since SHA3 HW engine in ZynqMPSoC does not support parallel processing of 2 hash requests, so we have changed our approach.
> Now to support parallel processing of 2 hash requests, software fallback is being used for init, update, final, export and import in the ZynqMP SHA driver.
> For digest, the calculation of SHA3 hash is done by the hardened SHA3 accelerator in Xilinx ZynqMP SoC.
>
I asked for parallel processing since I didnt see any locking or way to prevent hardware to be used in the same time.
But the final work is done by a firmware call, so my knowledge stop here.
> Following tests have been done for the driver:
> - Enabled kernel self tests and extra run-time crypto self tests
> - Tested SHA hash computation for different sizes of data using userspace application
> - Tested SHA hash computation using multiple updates of data using userspace application
> - Tested parallel hash computation
> - Tested using the tcrypt module
>
This should be in the cover letter.
Regards
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-22 9:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 19:14 [PATCH V2 0/4] crypto: Add Xilinx ZynqMP SHA3 driver support Harsha
2022-02-17 19:14 ` Harsha
2022-02-17 19:14 ` [PATCH V2 1/4] drivers: crypto: Updated Makefile for xilinx subdirectory Harsha
2022-02-17 19:14 ` Harsha
2022-02-17 19:14 ` [PATCH V2 2/4] firmware: xilinx: Add ZynqMP SHA API for SHA3 functionality Harsha
2022-02-17 19:14 ` Harsha
2022-02-18 9:43 ` Corentin Labbe
2022-02-18 9:43 ` Corentin Labbe
2022-02-21 12:17 ` Harsha Harsha
2022-02-21 12:17 ` Harsha Harsha
2022-02-21 13:08 ` Harsha Harsha
2022-02-21 13:08 ` Harsha Harsha
2022-02-22 9:47 ` Corentin Labbe [this message]
2022-02-22 9:47 ` Corentin Labbe
2022-02-17 19:14 ` [PATCH V2 3/4] crypto: xilinx: Add Xilinx SHA3 driver Harsha
2022-02-17 19:14 ` Harsha
2022-02-22 10:01 ` Corentin Labbe
2022-02-22 10:01 ` Corentin Labbe
2022-02-23 9:45 ` Harsha Harsha
2022-02-23 9:45 ` Harsha Harsha
2022-02-17 19:14 ` [PATCH V2 4/4] MAINTAINERS: Add maintainer for Xilinx ZynqMP " Harsha
2022-02-17 19:14 ` Harsha
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=YhSxF5nDzwsY9BFS@Red \
--to=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=git@xilinx.com \
--cc=harshah@xilinx.com \
--cc=harshj@xilinx.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=saratcha@xilinx.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.