RE: [PATCH V2] x86/split_lock: Add sysctl to control the misery mode

[Luck, Tony]

Looks reasonable.

Are these games multi-threaded with split locks happening on multiple CPUs in parallel?
If they are, then skipping both the 10ms delay and the serialization is needed.

But if split locks are only from one CPU at a time, then possibly it would have
been enough to just have this mitigation skip the:

+		if (msleep_interruptible(10) > 0)
+			return;

Maybe best not to second guess. You have left the default as "mitigation on",
so I'm happy.

-Tony