All of lore.kernel.org
 help / color / mirror / Atom feed
From: Surendran Kanagaraj <surenkj@amazon.com>
To: <jarkko@kernel.org>
Cc: <peterhuewe@gmx.de>, <jgg@ziepe.ca>,
	<linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<leitao@debian.org>, <nh-open-source@amazon.com>,
	<graf@amazon.de>, <gunnarku@amazon.com>, <joshlev@amazon.com>
Subject: Re: [PATCH v2 2/2] tpm_crb: Raise durations for Amazon NitroTPM
Date: Mon, 19 Oct 2026 18:27:13 +0000	[thread overview]
Message-ID: <20261019182713.57308-1-surenkj@amazon.com> (raw)
In-Reply-To: <atLD-d1v1B8ARv7x@kernel.org>

On Sat, Oct 17, 2026 at 03:40:25AM +0300, Jarkko Sakkinen wrote:
> On Sat, Oct 17, 2026 at 03:31:32AM +0300, Jarkko Sakkinen wrote:
> > Yeah so this needs a bit more redesign and while it is a possible
> > way to address all these issues I don't believe it is best possible
> > way imaginable to do something that lasts long-term.
> >
> > I don't want to go into concrete proposals because then I would have
> > to really engineer the whole change while at it because I would
> > likely try a number of approaches out. I.e. just a bit more effort
> > and innovation please.
>
> I can give this:
>
> 1. Map the whole flow how we fluctuate values of durations.
> 2. Think that if you were starting from zero how would you design a
>    unified and coherent flow. This includes all the callbacks and both TPM
>    1.x and TPM 2.0.
> 3. Redo the flow based on that premise.
>
> I.e., break more things with consideration and if it goes over the
> top then we attenuate the changes where needed.

Thanks for the pointers Jarkko. Will work out a design and send a
proposal.

Surendran

  reply	other threads:[~2026-10-19 18:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16  4:37 [PATCH v2 0/2] tpm: Handle transient NitroTPM unavailability Surendran Kanagaraj
2026-10-16  4:37 ` [PATCH v2 1/2] tpm: Add support for updating TPM2 durations Surendran Kanagaraj
2026-10-17  0:12   ` Jarkko Sakkinen
2026-10-17  0:19     ` Jarkko Sakkinen
2026-10-16  4:37 ` [PATCH v2 2/2] tpm_crb: Raise durations for Amazon NitroTPM Surendran Kanagaraj
2026-10-16 16:27   ` Jonathan McDowell
2026-10-16 16:38     ` Graf (AWS), Alexander
2026-10-17  0:28       ` Jarkko Sakkinen
2026-10-17  0:31   ` Jarkko Sakkinen
2026-10-17  0:40     ` Jarkko Sakkinen
2026-10-19 18:27       ` Surendran Kanagaraj [this message]
2026-10-19 18:36         ` Jarkko Sakkinen
2026-10-19 18:45           ` Jarkko Sakkinen

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=20261019182713.57308-1-surenkj@amazon.com \
    --to=surenkj@amazon.com \
    --cc=graf@amazon.de \
    --cc=gunnarku@amazon.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=joshlev@amazon.com \
    --cc=leitao@debian.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nh-open-source@amazon.com \
    --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 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.