From: Paul Gofman <pgofman@codeweavers.com>
To: Dave Hansen <dave.hansen@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
tony.luck@intel.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, luto@kernel.org, kernel-dev@igalia.com,
kernel@gpiccoli.net, Fenghua Yu <fenghua.yu@intel.com>,
Joshua Ashton <joshua@froggi.es>, Pavel Machek <pavel@denx.de>,
Pierre-Loup Griffais <pgriffais@valvesoftware.com>,
Melissa Wen <mwen@igalia.com>
Subject: Re: [PATCH] x86/split_lock: Restore warn mode (and add a new one) to avoid userspace regression
Date: Thu, 29 Sep 2022 12:23:58 -0500 [thread overview]
Message-ID: <90ec75f7-f094-b7ac-a635-0c320cc94bcb@codeweavers.com> (raw)
In-Reply-To: <ecbc58bc-a250-cf39-dea6-9b0b1c3e6503@intel.com>
On 9/29/22 11:26, Dave Hansen wrote:
> Let's be precise here, though. It isn't that folks can't play. It's
> that we *intentionally* put something in place that kept them from
> playing. They can play just fine after disabling split lock detection.
I guess that the statement that they can play is arguable. To do it, the
player (even capabale and willing to go as far as tweaking kernel
options, which alone may be a showstopper for the game to be called
playable) should get aware that the issue they are having can be solved
this way. IMO such level of involvement effectively means that a user
who is not technically advanced and not perceiving troubleshooting Linux
specific issues as a part of game play just can't play it.
next prev parent reply other threads:[~2022-09-29 17:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 14:21 Guilherme G. Piccoli
2022-09-28 20:24 ` Luck, Tony
2022-09-28 20:50 ` Joshua Ashton
2022-09-28 20:56 ` Guilherme G. Piccoli
2022-10-06 20:15 ` Thomas Gleixner
2022-10-06 20:58 ` Guilherme G. Piccoli
2022-10-06 9:04 ` Pavel Machek
2022-10-06 15:07 ` Guilherme G. Piccoli
2022-09-28 21:50 ` Dave Hansen
2022-09-29 14:57 ` Guilherme G. Piccoli
2022-09-29 15:17 ` Dave Hansen
2022-09-29 15:30 ` Guilherme G. Piccoli
2022-09-29 16:26 ` Dave Hansen
2022-09-29 17:15 ` Guilherme G. Piccoli
2022-09-29 17:23 ` Paul Gofman [this message]
2022-09-29 15:37 ` Luck, Tony
2022-10-30 16:13 ` Lukas Straub
2022-09-29 17:17 ` Zebediah Figura
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=90ec75f7-f094-b7ac-a635-0c320cc94bcb@codeweavers.com \
--to=pgofman@codeweavers.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=gpiccoli@igalia.com \
--cc=hpa@zytor.com \
--cc=joshua@froggi.es \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mwen@igalia.com \
--cc=pavel@denx.de \
--cc=pgriffais@valvesoftware.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--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
Powered by JetHome