mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Surendran Kanagaraj <surenkj@amazon.com>
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 21:45:16 +0300	[thread overview]
Message-ID: <atZlPHQH9c4akiKl@kernel.org> (raw)
In-Reply-To: <atZjPERR854RL0Yk@kernel.org>

On Mon, Oct 19, 2026 at 09:36:48PM +0300, Jarkko Sakkinen wrote:
> Yeah, this is also a theme, as generally the tone of kernel development
> has changed to be slightly more intrusive than before in the sense that
> addressing architectural issue is often better strategy than doing
> minimal effort as per code changes.
> 
> This is because it is the way we actually decrease the LLM bug fix
> activity. Implementation mistakes caused by the more bullish approach
> has factors lower price tag, if it can affect the rate and density
> of LLM storms.
> 
> This is why e.g., I've put out a patch set that departs assoc_array
> from kernel, and replaces it with rhashtable. This way we destroy
> nests instead of mosquitos.

Within limits and not over the top of course but like if something is
not working out for you look at one factor more generic problem and
solve that. This way many quality issues get gradually addressed
and it is actual antidote for LLM infections :-)

> 
> > 
> > Surendran
> 
> Br, Jarkko

Br, Jarkko

      reply	other threads:[~2026-10-19 18:45 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
2026-10-19 18:36         ` Jarkko Sakkinen
2026-10-19 18:45           ` Jarkko Sakkinen [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=atZlPHQH9c4akiKl@kernel.org \
    --to=jarkko@kernel.org \
    --cc=graf@amazon.de \
    --cc=gunnarku@amazon.com \
    --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 \
    --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®