https://bugs.winehq.org/show_bug.cgi?id=47571
Shmerl shtetldik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shtetldik@gmail.com
--- Comment #3 from Shmerl shtetldik@gmail.com --- According to: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1529309.html
When enabled, however, UMIP will change the behavior that certain applications expect from the operating system. For instance, programs running on WineHQ and DOSEMU2 rely on some of these instructions to function. [...] In order to not change the behavior of the system (i.e., a SIGSEGV signal should not be generated when using these instructions), this implementation traps the #GP fault generated by the CPU and emulates SGDT, SIDT and SMSW. with dummy returned values. This should be sufficient to not break the applications mentioned above.
Does this mean that workaround is broken and Wine is expecting something else?
Apparently Zen 2 processors are practically first ones to provide UMIP, so may be that workaround was never tested before on actual hardware that supports it.