[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7403891b-c84c-d0e5-e6e6-caf1bd4fcf51@igalia.com>
Date: Thu, 6 Oct 2022 12:07:16 -0300
From: "Guilherme G. Piccoli" <gpiccoli@...lia.com>
To: Pavel Machek <pavel@...x.de>, "Luck, Tony" <tony.luck@...el.com>,
"x86@...nel.org" <x86@...nel.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>
Cc: "tglx@...utronix.de" <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>, "hpa@...or.com" <hpa@...or.com>,
"Lutomirski, Andy" <luto@...nel.org>,
"kernel-dev@...lia.com" <kernel-dev@...lia.com>,
"kernel@...ccoli.net" <kernel@...ccoli.net>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
Joshua Ashton <joshua@...ggi.es>,
Paul Gofman <pgofman@...eweavers.com>,
Pierre-Loup Griffais <pgriffais@...vesoftware.com>,
Melissa Wen <mwen@...lia.com>
Subject: Re: [PATCH] x86/split_lock: Restore warn mode (and add a new one) to
avoid userspace regression
On 06/10/2022 06:04, Pavel Machek wrote:
> [...]
>> Why not just use the workaround suggested in that bug report:
>>
>> "so manual switching from default setting to split_lock_detect=off helps as workaround here"
>>
>> If you add this extra mode, I'm going to argue that the kernel default
>> should be "seq" rather than "warn". So these game players will need
>> to add a split_lock_detect=off (or warn) option.
>
> Kernel should not cause userland regressions, and this is one. That
> should make it pretty clear what the solution is.
>
> And no, I don't like CONFIG option, either.
Thanks for your opinion Pavel! Good thing is that seems everybody at
least understands the problem exists and is affecting userspace.
Now, about the action we should take: what if we go with a revert in
this "misery factor" based on Dave's reasoning? I have a patch ready and
tested, let me know otherwise or I'll submit it as a V2 by the end of
this week.
Cheers,
Guilherme
Powered by blists - more mailing lists