From: Dave Hansen <dave.hansen@linux.intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [GIT PULL] x86/splitlock for 6.2
Date: Mon, 12 Dec 2022 11:15:24 -0800 [thread overview]
Message-ID: <20221212191524.553244-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull some x86/splitlock changes for v6.2.
This includes a single change which enables users to reduce the
penalty inflicted on split lock users. There are some
proprietary, binary-only games which because entirely unplayable
with the old penalty.
Anyone opting into the new mode is, of course, more exposed to
the DoS nasitness inherent with split locks, but they can play
their games again.
--
The following changes since commit f0c4d9fc9cc9462659728d168387191387e903cc:
Linux 6.1-rc4 (2022-11-06 15:07:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_splitlock_for_6.2
for you to fetch changes up to 727209376f4998bc84db1d5d8af15afea846a92b:
x86/split_lock: Add sysctl to control the misery mode (2022-11-10 10:14:22 -0800)
----------------------------------------------------------------
Add a sysctl to control the split lock misery mode
----------------------------------------------------------------
Guilherme G. Piccoli (1):
x86/split_lock: Add sysctl to control the misery mode
Documentation/admin-guide/sysctl/kernel.rst | 23 +++++++++++
arch/x86/kernel/cpu/intel.c | 63 ++++++++++++++++++++++++-----
2 files changed, 76 insertions(+), 10 deletions(-)
next reply other threads:[~2022-12-12 19:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 19:15 Dave Hansen [this message]
2022-12-12 22:46 ` [GIT PULL] x86/splitlock for 6.2 pr-tracker-bot
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=20221212191524.553244-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).