Messages in this thread | | | Date | Wed, 28 Sep 2022 14:50:00 -0700 | Subject | Re: [PATCH] x86/split_lock: Restore warn mode (and add a new one) to avoid userspace regression | From | Dave Hansen <> |
| |
I really don't like the idea of *both* a new boot parameter and a new Kconfig option.
The warning mode worked as intended in this case because it got a user to file a bug and that bug report made it back to us. It's kinda funny to respond to that report by reducing the misery.
On the other hand, all the report resulted in was finger-pointing at a binary Windows applications that neither we nor probably anybody else can do anything about.
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.
The other option is to wait and see if there's any kind of pattern with these reports.
| |