mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Javier Pello <devel@otheo.eu>,
	linux-kernel@vger.kernel.org, x86@kernel.org,
	 Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/1] x86/mm/pae: Align up pteval_t, pmdval_t and pudval_t to avoid split locks
Date: Thu, 4 Apr 2024 14:55:20 -0700	[thread overview]
Message-ID: <Zg8hyG__NJZrB-ju@google.com> (raw)
In-Reply-To: <8ae52273-7b79-46b7-9cd5-2a0c401311c3@intel.com>

On Thu, Apr 04, 2024, Dave Hansen wrote:
> On 4/4/24 08:26, Sean Christopherson wrote:
> > In other words, practically speaking this isn't about supporting a new hardware
> > feature on 32-bit kernels, it's about preserving performance in real world
> > scenarios when running 32-bit kernels on new hardware.
> 
> Realistically, most of the 32-bit kernels in the world are going to be
> *OLD* distros, right?  Old CentOS/RHEL/SLES kernels from before the
> kernel had split lock detection, or split lock fixes.  Those trip over
> VMM split lock detection now, and presumably will forever.
> 
> I suspect new CentOS/RHEL/SLES kernels that have split lock detection
> all happened after 32-bit support was dropped from those distros.
> 
> I think that basically leaves Debian.  Someone would need to:
> 
>  1. Make a *new* 32-bit Debian distro install (or one of the other
>     less common distros that still do 32-bit)
>  2. Run it on hardware with split lock detection
>  3. On a VMM that enables split lock detection
>  4. Stay close enough to mainline to get split lock fixes (like from
>     this thread)
>  5. Care about performance, despite *ACTIVELY* choosing a 32-bit distro
>     on 64-bit hardware in 2024
>
> Those steps are certainly possible.  I'm just not sure how much trouble
> we want to go to in 2024 to support people that choose new 32-bit
> distros and desire performance.

I'm worried about a scenario where the throttling is so bad that it's not a perf
issue, but a functional issue ("performance" was a bad choice of word).

I do agree that the probability of this being a real problem is super low, but at
the same time it doesn't seem too onerous to clean up.  And in the unlikely case
that this does cause a problem, the pain on our end can be quite high.

> It feels to me to be approaching "I want a pony" territory.
> 
> Or am I just lacking empathy today? :)

Nah, I'm probably asking for a pony, but AFAICT it's a pretty cheap pony.

      reply	other threads:[~2024-04-04 21:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01 16:54 [PATCH 0/1] Split lock detected in kernel mode on x86-32 with PAE Javier Pello
2024-04-01 16:57 ` [PATCH 1/1] x86/mm/pae: Align up pteval_t, pmdval_t and pudval_t to avoid split locks Javier Pello
2024-04-01 17:56   ` Dave Hansen
2024-04-02 17:23     ` Javier Pello
2024-04-02 17:43       ` Dave Hansen
2024-04-03  7:57         ` Ingo Molnar
2024-04-03 11:08           ` Brian Gerst
2024-04-04  7:56             ` Ingo Molnar
2024-04-04 15:36               ` Brian Gerst
2024-04-04 16:29                 ` Dave Hansen
2024-04-03 15:54         ` Javier Pello
2024-04-03 15:58           ` Dave Hansen
2024-04-04 15:26             ` Sean Christopherson
2024-04-04 18:31               ` Dave Hansen
2024-04-04 21:55                 ` Sean Christopherson [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=Zg8hyG__NJZrB-ju@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=devel@otheo.eu \
    --cc=hpa@zytor.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®