From: David Laight <david.laight.linux@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Borislav Petkov <bp@alien8.de>, 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: Fri, 31 Jul 2026 10:14:25 +0100 [thread overview]
Message-ID: <20260731101425.3cdf139b@pumpkin> (raw)
In-Reply-To: <20260731084656.GF776954@noisy.programming.kicks-ass.net>
On Fri, 31 Jul 2026 10:46:56 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Jul 30, 2026 at 11:24:39AM -0700, Borislav Petkov wrote:
> > On Thu, Jul 30, 2026 at 07:31:04PM +0200, Peter Zijlstra wrote:
> > > But also, nah:
> > >
> > > https://support.arm.com/documentation/dui0802/b/A64-General-Instructions/TLBI
> > >
> > > "TLBI - TLB invalidate operation."
> >
> > Yap, that's what I meant.
> >
> > > tlbi={ipi,broadcast}
> > >
> > > Anyway, INVLPGB stands for INVaLidate PaGe Broadcast, ain'ted that hard
> > > :-) Also, you know who to complain to for that instruction :-)
> >
> > Too late for that. :)
> >
> > "tlbi=broadcast" is a bit much to type: imagine you're hunched over some box
> > in the server room, like Spiderman, crouching between racks and balancing the
> > keyboard on some old pile of cables... :-P
>
> There is IPMI and other fancy remote management stuff these days. There
> is no reason to suffer hearing loss for entering server rooms anymore
> :-)
The real problem is typing while wearing ski gloves...
David
>
> > So how about shorter:
> >
> > "tlbi=bcast"
> > "tlbi=ipi"
> >
> > ?
> >
> > We probably won't need to write "bcast" at all, actually, because that would
> > be the default. So "tlbi=ipi" only. Yeah, that's good.
>
> Didn't we have a case where INVLPGB was disabled due to firmware or
> something? I was thinking tlbi=broadcast could be used to force enable
> it or something.
>
> Anyway, if that case don't exist, then yeah.
>
next prev parent reply other threads:[~2026-07-31 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 0:43 [PATCH] add tlbi=off to disable INVLPGB 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
2026-07-30 18:24 ` Borislav Petkov
2026-07-31 8:46 ` Peter Zijlstra
2026-07-31 9:14 ` David Laight [this message]
2026-07-31 11:47 ` Rik van Riel
2026-07-31 18:32 ` Borislav Petkov
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=20260731101425.3cdf139b@pumpkin \
--to=david.laight.linux@gmail.com \
--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=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