From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
Peter Huewe <peterhuewe@gmx.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jens Wiklander <jens.wiklander@linaro.org>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Naveen N Rao <naveen@kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
linuxppc-dev@lists.ozlabs.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-integrity@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Sumit Garg <sumit.garg@kernel.org>,
linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH v3 4/4] tpm/tpm_svsm: support TPM_CHIP_FLAG_SYNC
Date: Wed, 30 Apr 2025 18:49:37 +0300 [thread overview]
Message-ID: <aBJGkSil1YAzSXsg@kernel.org> (raw)
In-Reply-To: <20250414145653.239081-5-sgarzare@redhat.com>
On Mon, Apr 14, 2025 at 04:56:53PM +0200, Stefano Garzarella wrote:
> From: Stefano Garzarella <sgarzare@redhat.com>
>
> This driver does not support interrupts, and receiving the response is
> synchronous with sending the command.
>
> So we can set TPM_CHIP_FLAG_SYNC to support synchronous send() and
> return responses in the same buffer used for commands. This way we
> don't need to implement recv() op.
>
> Keep using the same pre-allocated buffer to avoid having to allocate
> it for each command. We need the buffer to have the header required by
> the SVSM protocol and the command contiguous in memory.
>
> Signed-off-by: Stefano Garzarella <sgarzare@redhat.com>
Similar comments, and a bit redundancy does not matter i.e., they can
have pretty much the same explanation.
> ---
> drivers/char/tpm/tpm_svsm.c | 27 +++++++++++----------------
> 1 file changed, 11 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/char/tpm/tpm_svsm.c b/drivers/char/tpm/tpm_svsm.c
> index d3ca5615b6f7..db1983072345 100644
> --- a/drivers/char/tpm/tpm_svsm.c
> +++ b/drivers/char/tpm/tpm_svsm.c
> @@ -25,38 +25,32 @@ struct tpm_svsm_priv {
> void *buffer;
> };
>
> -static int tpm_svsm_send(struct tpm_chip *chip, u8 *buf, size_t len,
> +static int tpm_svsm_send(struct tpm_chip *chip, u8 *buf, size_t cmd_len,
> size_t buf_size)
> {
> struct tpm_svsm_priv *priv = dev_get_drvdata(&chip->dev);
> int ret;
>
> - ret = svsm_vtpm_cmd_request_fill(priv->buffer, 0, buf, len);
> + ret = svsm_vtpm_cmd_request_fill(priv->buffer, 0, buf, cmd_len);
> if (ret)
> return ret;
>
> /*
> * The SVSM call uses the same buffer for the command and for the
> - * response, so after this call, the buffer will contain the response
> - * that can be used by .recv() op.
> + * response, so after this call, the buffer will contain the response.
> + *
> + * Note: we have to use an internal buffer because the device in SVSM
> + * expects the svsm_vtpm header + data to be physically contiguous.
> */
> - return snp_svsm_vtpm_send_command(priv->buffer);
> -}
> -
> -static int tpm_svsm_recv(struct tpm_chip *chip, u8 *buf, size_t len)
> -{
> - struct tpm_svsm_priv *priv = dev_get_drvdata(&chip->dev);
> + ret = snp_svsm_vtpm_send_command(priv->buffer);
> + if (ret)
> + return ret;
>
> - /*
> - * The internal buffer contains the response after we send the command
> - * to SVSM.
> - */
> - return svsm_vtpm_cmd_response_parse(priv->buffer, buf, len);
> + return svsm_vtpm_cmd_response_parse(priv->buffer, buf, buf_size);
> }
>
> static struct tpm_class_ops tpm_chip_ops = {
> .flags = TPM_OPS_AUTO_STARTUP,
> - .recv = tpm_svsm_recv,
> .send = tpm_svsm_send,
> };
>
> @@ -85,6 +79,7 @@ static int __init tpm_svsm_probe(struct platform_device *pdev)
>
> dev_set_drvdata(&chip->dev, priv);
>
> + chip->flags |= TPM_CHIP_FLAG_SYNC;
> err = tpm2_probe(chip);
> if (err)
> return err;
> --
> 2.49.0
>
BR, Jarkko
next prev parent reply other threads:[~2025-04-30 16:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 14:56 [PATCH v3 0/4] tpm: add support for sync send() and use it in ftpm and svsm drivers Stefano Garzarella
2025-04-14 14:56 ` [PATCH v3 1/4] tpm: add buf_size parameter in the .send callback Stefano Garzarella
2025-04-30 15:39 ` Jarkko Sakkinen
2025-05-06 12:56 ` Stefano Garzarella
2025-05-08 20:00 ` Jarkko Sakkinen
2025-04-14 14:56 ` [PATCH v3 2/4] tpm: support devices with synchronous send() Stefano Garzarella
2025-04-30 15:41 ` Jarkko Sakkinen
2025-04-14 14:56 ` [PATCH v3 3/4] tpm/tpm_ftpm_tee: support TPM_CHIP_FLAG_SYNC Stefano Garzarella
2025-04-14 14:59 ` Stefano Garzarella
2025-04-28 7:49 ` Sumit Garg
2025-04-30 15:47 ` Jarkko Sakkinen
2025-05-06 13:03 ` Stefano Garzarella
2025-04-14 14:56 ` [PATCH v3 4/4] tpm/tpm_svsm: " Stefano Garzarella
2025-04-30 15:49 ` Jarkko Sakkinen [this message]
2025-05-06 13:06 ` Stefano Garzarella
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=aBJGkSil1YAzSXsg@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alexandre.belloni@bootlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=claudiu.beznea@tuxon.dev \
--cc=jens.wiklander@linaro.org \
--cc=jgg@ziepe.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=naveen@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=npiggin@gmail.com \
--cc=peterhuewe@gmx.de \
--cc=sgarzare@redhat.com \
--cc=sumit.garg@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;
as well as URLs for NNTP newsgroup(s).