From: Rik van Riel <riel@surriel.com>
To: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH] x86,cpu: add X86_FEATURE_INVLPGB flag
Date: Wed, 25 Sep 2024 12:46:39 -0400 [thread overview]
Message-ID: <628c91f76feaf6e29522c8fef5d9351ba6104183.camel@surriel.com> (raw)
In-Reply-To: <24A7815F-E21F-45D3-9784-109B5932B41C@alien8.de>
On Wed, 2024-09-25 at 08:45 +0100, Borislav Petkov wrote:
> On September 24, 2024 11:00:13 PM GMT+01:00, Rik van Riel
> <riel@surriel.com> wrote:
> > Add the definition for the X86_FEATURE_INVLPGB CPUID flag.
> >
> > Tested by booting a kernel with this change on an AMD Milan system,
> > and making sure the "invlpgb" flag shows up in /proc/cpuinfo
>
> Why?
>
I would like to avoid TLB flush IPIs for the top N (maybe 8 or 16?)
TLB flushing processes in the system. We can figure out what these
processes are by keeping a score of TLB flushes * number of CPUs over
some time period.
That seems like something AMD CPUs might be able to do, without
running out of PCIDs even on larger systems.
The TLB flush IPIs are taking a considerable amount of compute
power across a large fleet, and is something I would like to
optimize.
--
All Rights Reversed.
next prev parent reply other threads:[~2024-09-25 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 22:00 Rik van Riel
2024-09-25 3:33 ` Xin Li
2024-09-25 14:05 ` Rik van Riel
2024-09-25 7:45 ` Borislav Petkov
2024-09-25 16:46 ` Rik van Riel [this message]
2024-09-26 8:10 ` 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=628c91f76feaf6e29522c8fef5d9351ba6104183.camel@surriel.com \
--to=riel@surriel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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®