Re: [PATCH] x86/split_lock: Restore warn mode (and add a new one) to avoid userspace regression

["Guilherme G. Piccoli" <gpiccoli@igalia.com>]

Two responses in one:

First, I like Tony's idea - heuristic based on CPU number seems to make
sense. This number could be purely based on CPU number with a hardcoded
value, or based in a Kconfig (after N CPUs, add misery).


Now, second part below, inline:

On 29/09/2022 13: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.
>

Agreed with your wording, would just maybe "s/put something/added a
policy" heheh


>> [...]
> They don't have to live with it.  They can turn it off.  That's why the
> command-line disable is there.
> 

If they know how to do it, right? I'd rather have it as a new
non-default mechanism or at least, a Kconfig option in which gamer
distros could tune for their users, so we're not requiring them to tune
x86-specific parameters to play some game.