mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Rik van Riel <riel@surriel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH] add tlbi=off to disable INVLPGB
Date: Thu, 30 Jul 2026 19:31:04 +0200	[thread overview]
Message-ID: <20260730173104.GB776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260730162318.GAamt6ds0siEVGwWlw@fat_crate.local>

On Thu, Jul 30, 2026 at 09:23:18AM -0700, Borislav Petkov wrote:
> On Thu, Jul 30, 2026 at 12:32:27PM +0200, Peter Zijlstra wrote:
> > TLBI stands for Translation Lookaside Buffer Invalidation.
> 
> ... instructions." Both ARM and AMD call it this. The usual abbreviation
> overload we're suffering from.

Same difference, that would mean disabling all TLB instructions :-) Very
much including the local invalidation used for IPI based TLB
invalidation.

But also, nah:

  https://support.arm.com/documentation/dui0802/b/A64-General-Instructions/TLBI

"TLBI - TLB invalidate operation."
  
> > So a command line that says: 'tlbi=off' means no move invalidation *at*all*.
> > This seems like a very bad option.
> > 
> > Please rename.
> 
> You suggest one. :-P
> 
> But it needs to be short and relatively easy to type. And "invlpgb" ain't easy
> and I can't tell you how many times I've seen it getting typoed.

  tlbi={ipi,broadcast}

Anyway, INVLPGB stands for INVaLidate PaGe Broadcast, ain'ted that hard
:-) Also, you know who to complain to for that instruction :-)

  reply	other threads:[~2026-07-30 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30  0:43 Rik van Riel
2026-07-30  1:44 ` Borislav Petkov
2026-07-30 10:32   ` Peter Zijlstra
2026-07-30 16:23     ` Borislav Petkov
2026-07-30 17:31       ` Peter Zijlstra [this message]
2026-07-30 18:24         ` Borislav Petkov
2026-07-31  8:46           ` Peter Zijlstra
2026-07-31  9:14             ` David Laight
2026-07-31 11:47             ` Rik van Riel
2026-07-31 18:32             ` Borislav Petkov
2026-08-06 15:54               ` [PATCH] x86/CPU: Add a tlbi= cmdline switch Borislav Petkov
2026-08-10 16:47 ` [tip: x86/urgent] " tip-bot2 for Rik van Riel

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=20260730173104.GB776954@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --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®