From: Dave Hansen <dave.hansen@intel.com>
To: Javier Pello <devel@otheo.eu>
Cc: 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: Wed, 3 Apr 2024 08:58:31 -0700 [thread overview]
Message-ID: <7db8d0a8-c668-44be-a348-58120a97fc2b@intel.com> (raw)
In-Reply-To: <20240403175407.f81ebc5cc3300ffa0c39f597@otheo.eu>
On 4/3/24 08:54, Javier Pello wrote:
> - The third way would be to disable split lock detection on x86-32.
> This can be as simple as setting the default to "none" in
> sld_state_setup(). Not the most elegant of solutions, but beats
> having unresponsive tasks.
>
> Would going for the first one be worth the trouble?
No, it's not worth it. Let's just disable split lock detection on
32-bit and move on with life.
next prev parent reply other threads:[~2024-04-03 15:58 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 [this message]
2024-04-04 15:26 ` Sean Christopherson
2024-04-04 18:31 ` Dave Hansen
2024-04-04 21:55 ` Sean Christopherson
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=7db8d0a8-c668-44be-a348-58120a97fc2b@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--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®