From: Arun Menon <armenon@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH v4 6/6] tpm_crb: Implement command and response chunking logic
Date: Mon, 26 Oct 2026 20:01:32 +0530 [thread overview]
Message-ID: <at9kRNac6oe_txwZ@fedora> (raw)
In-Reply-To: <at57uzLtUZ4z97LL@kernel.org>
Hi Jarkko,
Thank you for the detailed feedback.
On Sun, Oct 25, 2026 at 11:59:23PM +0200, Jarkko Sakkinen wrote:
> On Mon, Oct 26, 2026 at 01:48:58AM +0530, Arun Menon wrote:
> > From: Arun Menon <armenon@redhat.com>
> >
> > With the introduction of support for Post Quantum Cryptography
> > algorithms in TPM, the commands and responses will grow in size.
> > Some TPMs have a physical hardware memory window (MMIO) that is
> > smaller than the commands we need to send.
>
> That is too loose scope, and its truth value will be degrading as time
> moves forward.
>
> Here's what I think about the topic and would look up:
>
> 1. TCG has defined this in a spec. I would point out the spec and
> section(s), and optionally also date when it was published (like
> "09/2025" or "Spring of 2024", nothing more granular than this).
Sure, I will add the spec detail, citing the TPM PC Client PTP (Platform
TPM Profile) with section number and date.
> 2. PQC will be probably a thing across the whole chip industry.
> This is why we need to support it not because of some random
> buffer shenanigans, right?
> 3. "Some TPMs" is inaccurate statement in a wrong way. I would be
> inaccurate too but how I would simplify the topic would come
> from an utilitirian angle.
yes, I understand. Any CRB TPM that gets the updated PQC-sized payloads
will hit the same MMIO-window limit.
>
> Regardless what future holds i.e., I would represent the set
> of PQC enabled TPMs and the set of chunking enabled TPMs as they
> were the same set. This type of self-deception is what engineering
> really is all about, overall ;-)
yes, its a PQC transition generally. I will mention that.
>
> Those are my verbose remarks or how I model this situation, which
> would synthesize into maybe 2-4 not that long sentences.
>
> > Therefore this commit
> > implements the core logic of sending/receiving data in chunks.
>
> I would remove this sentence because it has no utilitirian use and
> does not make anyone smarter, other than you get the feeling that
> "I should probably pretend that I know what the chunks are".
yes, will remove this line.
>
> Add a short paragrap tell us what the heck they are reference to
> section is great but putting the concept in nutshell without having
> to immediately peak at it would be great.
>
> >
> > Instead of sending the whole command at once, the driver now sends it in
> > small chunks. After each chunk, it signals the TPM using a nextChunk
>
> This is a bit loose form of expression and I'm not fan of qualitative
> size definitions.
>
> Example: "Send the command split into chunks."
>
> That's really all information content of the first sentence.
>
> > signal, and waits for the TPM to consume the data. Once the final piece
> > is delivered, the driver signals the TPM to begin execution by toggling
> > the start invoke bit. We use the same logic in reverse to read large
> > responses from the TPM.
>
> This is abstracting and encapsulating the meat of the code change.
>
> Remarks:
>
> - The list of the added constants.
yes, will add them
> - Speak how the CRB registers are used.
yes.
> - Stuff is heavily moved around but I don't see anything that would
> help me to understand the reorg part. This is important because
> that gives better map to navigate and check if this patch
> could be split (I don't know yet).
I will split the 6th patch in to 2. The preparation patch will put the
existing crb_send()/crb_recv() into
tpm_crb_send_no_chunks()/tpm_crb_recv_no_chunks().
Also, I will forward declare tpm_crb_start() (required by
tpm_crb_recv_chunks()) so that the diff is clean.
> - Go through each location where use the word "signal". It's used
> like a solution encapsulator.
I will explain the use of registers briefly. The registers were
introduced in a former patch.
>
> When asked this much details and stuff I personally can recommend
> more imperative writing style (see the examples). It has friction
> because you can move sentence forward only when you get.
>
> >
> > This allows the driver to handle large payloads even when the hardware
> > interface has limited memory. This kernel-side support corresponds to
> > the backend implementation in QEMU [1]. QEMU reassembles the chunks
> > before passing them to the TPM emulator.
> >
> > [1] https://lore.kernel.org/qemu-devel/20260506075813.120781-1-armenon@redhat.com/
> >
> > Signed-off-by: Arun Menon <armenon@redhat.com>
> > ---
> > drivers/char/tpm/tpm_crb.c | 215 +++++++++++++++++++++++++++++--------
> > 1 file changed, 173 insertions(+), 42 deletions(-)
> >
> > diff --git a/drivers/char/tpm/tpm_crb.c b/drivers/char/tpm/tpm_crb.c
> > index 31f530744e90..8b2aaa109fc4 100644
> > --- a/drivers/char/tpm/tpm_crb.c
> > +++ b/drivers/char/tpm/tpm_crb.c
> > @@ -105,11 +105,13 @@ struct crb_priv {
> > u8 __iomem *cmd;
> > u8 __iomem *rsp;
> > u32 cmd_size;
> > + u32 rsp_size;
> > u32 smc_func_id;
> > u32 __iomem *pluton_start_addr;
> > u32 __iomem *pluton_reply_addr;
> > u8 ffa_flags;
> > u8 ffa_attributes;
> > + u32 intf_id;
> > };
> >
> > struct tpm2_crb_smc {
> > @@ -369,38 +371,6 @@ static u8 crb_status(struct tpm_chip *chip)
> > return sts;
> > }
> >
> > -static int crb_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> > -{
> > - struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > - unsigned int expected;
> > -
> > - /* A sanity check that the upper layer wants to get at least the header
> > - * as that is the minimum size for any TPM response.
> > - */
> > - if (count < TPM_HEADER_SIZE)
> > - return -EIO;
> > -
> > - /* If this bit is set, according to the spec, the TPM is in
> > - * unrecoverable condition.
> > - */
> > - if (ioread32(&priv->regs_t->ctrl_sts) & CRB_CTRL_STS_ERROR)
> > - return -EIO;
> > -
> > - /* Read the first 8 bytes in order to get the length of the response.
> > - * We read exactly a quad word in order to make sure that the remaining
> > - * reads will be aligned.
> > - */
> > - memcpy_fromio(buf, priv->rsp, 8);
> > -
> > - expected = be32_to_cpup((__be32 *)&buf[2]);
> > - if (expected > count || expected < TPM_HEADER_SIZE)
> > - return -EIO;
> > -
> > - memcpy_fromio(&buf[8], &priv->rsp[8], expected - 8);
> > -
> > - return expected;
> > -}
> > -
> > static int crb_do_acpi_start(struct tpm_chip *chip)
> > {
> > union acpi_object *obj;
> > @@ -472,17 +442,71 @@ static int tpm_crb_start(struct tpm_chip *chip, u32 start_cmd)
> > return rc;
> > }
> >
> > +static int tpm_crb_send_no_chunks(struct tpm_chip *chip, u8 *buf, size_t len)
> > +{
> > + struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > + int rc;
> > +
> > + memcpy_toio(priv->cmd, buf, len);
> > +
> > + /* Make sure that cmd is populated before issuing start. */
> > + wmb();
> > +
> > + rc = tpm_crb_start(chip, CRB_START_INVOKE);
> > + if (rc)
> > + return rc;
> > +
> > + return crb_try_pluton_doorbell(priv, false);
> > +}
> > +
> > +static int tpm_crb_send_chunks(struct tpm_chip *chip, u8 *buf, size_t len)
> > +{
> > + struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > + size_t offset = 0;
> > + size_t chunk_size;
> > + int rc;
> > +
> > + while (offset < len) {
> > + chunk_size = min_t(size_t, len - offset, priv->cmd_size);
> > +
> > + if (chunk_size == 0)
> > + break;
> > +
> > + memcpy_toio(priv->cmd, buf + offset, chunk_size);
> > + offset += chunk_size;
> > +
> > + /* Make sure that cmd is populated before issuing start. */
> > + wmb();
> > + if (offset < len) {
> > + rc = tpm_crb_start(chip, CRB_START_NEXT_CHUNK);
> > + if (rc)
> > + return rc;
> > + if (!crb_wait_for_reg_32(&priv->regs_t->ctrl_start,
> > + CRB_START_NEXT_CHUNK, 0,
> > + TPM2_TIMEOUT_C)) {
>
> I'd split these calls into two lines:
>
> expired = !crb_wait_for_reg_32( ... );
> if (expired) {
>
>
>
yes will do it.
> > + dev_err(&chip->dev,
> > + "Timeout waiting for backend to consume chunk\n");
> > + return -ETIME;
> > + }
> > + } else {
> > + rc = tpm_crb_start(chip, CRB_START_INVOKE);
> > + if (rc)
> > + return rc;
> > + }
> > + }
> > +
> > + return crb_try_pluton_doorbell(priv, false);
> > +}
> > static int crb_send(struct tpm_chip *chip, u8 *buf, size_t bufsiz, size_t len)
> > {
> > struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > - int rc = 0;
> >
> > /* Zero the cancel register so that the next command will not get
> > * canceled.
> > */
> > iowrite32(0, &priv->regs_t->ctrl_cancel);
> >
> > - if (len > priv->cmd_size) {
> > + if (len > priv->cmd_size && !(priv->intf_id & CRB_INTF_CAP_CRB_CHUNK)) {
> > dev_err(&chip->dev, "invalid command count value %zd %d\n",
> > len, priv->cmd_size);
> > return -E2BIG;
> > @@ -492,16 +516,115 @@ static int crb_send(struct tpm_chip *chip, u8 *buf, size_t bufsiz, size_t len)
> > if (priv->sm == ACPI_TPM2_COMMAND_BUFFER_WITH_PLUTON)
> > __crb_cmd_ready(&chip->dev, priv, chip->locality);
> >
> > - memcpy_toio(priv->cmd, buf, len);
> > + if (len <= priv->cmd_size)
> > + return tpm_crb_send_no_chunks(chip, buf, len);
> >
> > - /* Make sure that cmd is populated before issuing start. */
> > - wmb();
> > + return tpm_crb_send_chunks(chip, buf, len);
> > +}
> >
> > - rc = tpm_crb_start(chip, CRB_START_INVOKE);
> > - if (rc)
> > - return rc;
> > +static int tpm_crb_recv_no_chunks(struct tpm_chip *chip, u8 *buf, size_t count)
> > +{
> > + struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > + unsigned int expected;
> >
> > - return crb_try_pluton_doorbell(priv, false);
> > + /* Read the first 8 bytes in order to get the length of the response.
> > + * We read exactly a quad word in order to make sure that the remaining
> > + * reads will be aligned.
> > + */
>
> When moving code not heavy mods should be done but we can fix this
> cosmetic glitch from the block comments at least.
>
> > + memcpy_fromio(buf, priv->rsp, 8);
> > +
> > + expected = be32_to_cpup((__be32 *)&buf[2]);
> > + if (expected > count || expected < TPM_HEADER_SIZE)
> > + return -EIO;
> > +
> > + memcpy_fromio(&buf[8], &priv->rsp[8], expected - 8);
> > +
> > + return expected;
> > +}
> > +
> > +static int tpm_crb_recv_chunks(struct tpm_chip *chip, u8 *buf, size_t count,
> > + unsigned int expected)
> > +{
> > + struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > + size_t offset = 0;
> > + size_t chunk_size;
> > + size_t first_read;
> > + int rc;
> > +
> > + if (expected > count)
> > + return -EIO;
> > + /*
> > + * Set chunk_size by comparing the size of the buffer that the upper
> > + * layer has allocated (count) to the hardware tpm limit (priv->rsp_size).
> > + * This is to prevent buffer overflow while writing to buf.
> > + */
> > + chunk_size = min_t(size_t, count, priv->rsp_size);
> > + if (chunk_size < 8)
> > + return -EIO;
> > +
> > + memcpy_fromio(buf, priv->rsp, 8);
> > +
> > + /*
> > + * Compare the actual size of the response we found in
> > + * the header to the chunk size
> > + */
> > + first_read = min_t(size_t, expected, chunk_size);
> > +
> > + memcpy_fromio(&buf[8], &priv->rsp[8], first_read - 8);
> > + offset = first_read;
> > +
> > + while (offset < expected) {
> > + rc = tpm_crb_start(chip, CRB_START_NEXT_CHUNK);
> > + if (rc)
> > + return rc;
> > +
> > + if (!crb_wait_for_reg_32(&priv->regs_t->ctrl_start,
> > + CRB_START_NEXT_CHUNK, 0,
> > + TPM2_TIMEOUT_C)) {
> > + dev_err(&chip->dev, "Timeout waiting for backend response\n");
> > + return -ETIME;
> > + }
> > +
> > + chunk_size = min_t(size_t, expected - offset, priv->rsp_size);
> > + memcpy_fromio(buf + offset, priv->rsp, chunk_size);
> > + offset += chunk_size;
> > + }
> > +
> > + return expected;
> > +}
> > +
> > +static int crb_recv(struct tpm_chip *chip, u8 *buf, size_t count)
> > +{
> > + struct crb_priv *priv = dev_get_drvdata(&chip->dev);
> > + unsigned int expected;
> > +
> > + /* A sanity check that the upper layer wants to get at least the header
> > + * as that is the minimum size for any TPM response.
> > + */
> > + if (count < TPM_HEADER_SIZE)
> > + return -EIO;
> > +
> > + /* If this bit is set, according to the spec, the TPM is in
> > + * unrecoverable condition.
> > + */
> > + if (ioread32(&priv->regs_t->ctrl_sts) & CRB_CTRL_STS_ERROR)
> > + return -EIO;
> > +
> > + /*
> > + * Peek at the first 8 bytes to determine the response size
> > + */
> > + expected = be32_to_cpup((__be32 *)&priv->rsp[2]);
> > +
> > + if (expected <= priv->rsp_size)
> > + return tpm_crb_recv_no_chunks(chip, buf, count);
> > +
> > + if (!(priv->intf_id & CRB_INTF_CAP_CRB_CHUNK)) {
> > + dev_err(&chip->dev,
> > + "Response larger than MMIO and chunking not supported\n");
> > + return -EIO;
> > + }
> > +
> > + return tpm_crb_recv_chunks(chip, buf, count, expected);
> > }
> >
> > static void crb_cancel(struct tpm_chip *chip)
> > @@ -728,6 +851,12 @@ static int crb_map_io(struct device *dev, struct crb_priv *priv,
> > goto out;
> > }
> >
> > + if (priv->regs_h)
> > + priv->intf_id = ioread32((u32 __iomem *)&priv->regs_h->intf_id);
> > +
> > + if (priv->intf_id & CRB_INTF_CAP_CRB_CHUNK)
> > + dev_info(dev, "CRB Chunking is supported by backend\n");
> > +
> > memcpy_fromio(&__rsp_pa, &priv->regs_t->ctrl_rsp_pa, 8);
> > rsp_pa = le64_to_cpu(__rsp_pa);
> > rsp_size = ioread32(&priv->regs_t->ctrl_rsp_size);
> > @@ -765,8 +894,10 @@ static int crb_map_io(struct device *dev, struct crb_priv *priv,
> > priv->rsp = priv->cmd;
> >
> > out:
> > - if (!ret)
> > + if (!ret) {
> > priv->cmd_size = cmd_size;
> > + priv->rsp_size = rsp_size;
> > + }
> >
> > __crb_go_idle(dev, priv, 0);
> >
> > --
> > 2.54.0
> >
>
> Let's take this easy as it can land earliest v7.5. It would be hard
> to miss that deadline so polishing all the details is the best way
> to go.
I agree. Thanks again.
>
> Br, Jarkko
>
Regards,
Arun Menon
prev parent reply other threads:[~2026-10-26 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 20:18 [PATCH v4 0/6] tpm_crb: Add command and response buffer chunking support Arun Menon
2026-10-25 20:18 ` [PATCH v4 1/6] tpm_crb: Add register definitions of TPM CRB chunking fields Arun Menon
2026-10-25 20:18 ` [PATCH v4 2/6] tpm_crb: Split start method into a separate header Arun Menon
2026-10-25 20:55 ` Jarkko Sakkinen
2026-10-26 14:28 ` Arun Menon
2026-10-25 20:56 ` Jarkko Sakkinen
2026-10-25 20:18 ` [PATCH v4 3/6] tpm_crb: Add start_cmd parameter to tpm_crb_start wrapper Arun Menon
2026-10-25 20:18 ` [PATCH v4 4/6] tpm: tis_i2c: Use local 4KB buffer to limit memory usage Arun Menon
2026-10-25 20:18 ` [PATCH v4 5/6] tpm: Increase TPM_BUFSIZE to 8kB for chunking support Arun Menon
2026-10-25 20:59 ` Jarkko Sakkinen
2026-10-25 21:00 ` Jarkko Sakkinen
2026-10-26 14:30 ` Arun Menon
2026-10-26 19:32 ` Jarkko Sakkinen
2026-10-25 20:18 ` [PATCH v4 6/6] tpm_crb: Implement command and response chunking logic Arun Menon
2026-10-25 21:59 ` Jarkko Sakkinen
2026-10-26 14:31 ` Arun Menon [this message]
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=at9kRNac6oe_txwZ@fedora \
--to=armenon@redhat.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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
all inboxes | Powered by JetHome®