lkml.org 
[lkml]   [2022]   [Sep]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] x86/split_lock: Restore warn mode (and add a new one) to avoid userspace regression
From
On 28/09/2022 18:50, Dave Hansen wrote:
>[...]
> It boils down to either:
> * The misery is good and we keep it as-is, or
> * The misery is bad and we kill it
>
> My gut says we should keep the warnings and kill the misery. The folks
> who are going to be able to fix the issues are probably also the ones
> looking at dmesg and don't need the extra hint from the misery. The
> folks running Windows games don't look at dmesg and just want to play
> their game without misery.
>

Hi Dave, thanks for your response. I really appreciated your reasoning,
and I think it's a good argument. In the end, adding misery would harm
the users that are unlikely to be able to fix (or at least, fix quickly)
the split lock situation, like games or legacy/proprietary code.

I have a revert removing the misery ready and tested, let me know if I
should submit it.

Cheers,


Guilherme

\
 
 \ /
  Last update: 2022-09-29 16:58    [W:0.146 / U:2.196 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site