From: Breno Leitao <leitao@debian.org>
To: Surendran Kanagaraj <surenkj@amazon.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
nh-open-source@amazon.com, Alexander Graf <graf@amazon.de>,
Gunnar Kudrjavets <gunnarku@amazon.com>,
Josh Levinson <joshlev@amazon.com>
Subject: Re: [PATCH 1/2] tpm: Add per-chip timeout for transient unavailability
Date: Fri, 25 Sep 2026 02:04:19 -0700 [thread overview]
Message-ID: <arY2qHhjv97W7WvK@gmail.com> (raw)
In-Reply-To: <20260923142834.16786-2-surenkj@amazon.com>
On Wed, Sep 23, 2026 at 02:28:33PM +0000, Surendran Kanagaraj wrote:
> Devices that have different timeout requirements than the TPM2 spec
Can you help us understand why this device doesn't follow the spec,
and why the quirk belongs in the kernel rather than being fixed in
the TPM2 itself?
Is NitroTPM a virtual TPM? If so, could the virtualization software
be fixed instead to follow the spec?
> @@ -241,6 +243,9 @@ ssize_t tpm_transmit(struct tpm_chip *chip, u8 *buf, size_t bufsiz)
> */
> memcpy(save, buf, save_size);
>
> + if (chip->busy_timeout_ms > max_delay_msec)
> + max_delay_msec = chip->busy_timeout_ms;
nit: this could use max() instead:
max_delay_msec = max(chip->busy_timeout_ms, max_delay_msec).
Also, should there be an upper bound?
> + if (duration < chip->busy_timeout_ms)
> + duration = chip->busy_timeout_ms;
>
> - return msecs_to_jiffies(TPM2_DURATION_DEFAULT);
> + return msecs_to_jiffies(duration);
What about something like this instead?
return msecs_to_jiffies(max_t(unsigned long, duration,
chip->busy_timeout_ms));
Thanks,
--breno
next prev parent reply other threads:[~2026-09-25 9:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 14:28 [PATCH 0/2] tpm: Handle transient NitroTPM unavailability Surendran Kanagaraj
2026-09-23 14:28 ` [PATCH 1/2] tpm: Add per-chip timeout for transient unavailability Surendran Kanagaraj
2026-09-25 9:04 ` Breno Leitao [this message]
2026-09-28 19:50 ` Surendran Kanagaraj
2026-09-29 22:15 ` Jarkko Sakkinen
2026-09-25 16:03 ` Jarkko Sakkinen
2026-09-29 13:21 ` Surendran Kanagaraj
2026-09-23 14:28 ` [PATCH 2/2] tpm_crb: Raise timeouts for Amazon NitroTPM Surendran Kanagaraj
2026-09-25 15:55 ` Jarkko Sakkinen
2026-09-28 21:09 ` Surendran Kanagaraj
2026-09-29 22:22 ` Jarkko Sakkinen
2026-09-30 19:15 ` Surendran Kanagaraj
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=arY2qHhjv97W7WvK@gmail.com \
--to=leitao@debian.org \
--cc=graf@amazon.de \
--cc=gunnarku@amazon.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=joshlev@amazon.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nh-open-source@amazon.com \
--cc=peterhuewe@gmx.de \
--cc=surenkj@amazon.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 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®