mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Lendacky <thomas.lendacky@amd.com>
To: Dave Hansen <dave.hansen@intel.com>,
	linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Nadav Amit <nadav.amit@gmail.com>,
	Rik van Riel <riel@surriel.com>
Subject: Re: [PATCH v2] x86/mm: Disable broadcast TLB flush when PCID is disabled
Date: Tue, 19 May 2026 16:21:52 -0500	[thread overview]
Message-ID: <fa159e76-1aa6-4c14-bf85-03a0e4c8a453@amd.com> (raw)
In-Reply-To: <126b60dd-f115-4e1a-8619-f4037a2b753d@intel.com>

On 5/19/26 14:49, Dave Hansen wrote:
> On 5/19/26 12:22, Tom Lendacky wrote:
>> Assisted-by: Claude:claude-opus-4.7
> 
> Can we please take it easy on the AI changelogs?
> 
> They're ... not great.
> 
> They spend an inordinate amount of time regurgitating what the code
> does. Even obvious stuff. They're not great at focusing on what matters.
> 
> Seriously, why waste the bytes to tell me what bits of RDX are used for
> the PCID for INVLPGB? Only the AI cares. No humans care.

Do you want a v3 with an updated commit message or do you want to
massage it? Either way works for me.

Thanks,
Tom


  reply	other threads:[~2026-05-19 21:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 19:22 Tom Lendacky
2026-05-19 19:28 ` Rik van Riel
2026-05-19 19:49 ` Dave Hansen
2026-05-19 21:21   ` Tom Lendacky [this message]
2026-05-19 21:47     ` Dave Hansen

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=fa159e76-1aa6-4c14-bf85-03a0e4c8a453@amd.com \
    --to=thomas.lendacky@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nadav.amit@gmail.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=tglx@kernel.org \
    --cc=x86@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

all inboxes | Powered by JetHome®