3 ms·

Nice. Does anyone know how this differs from using KVM for this like gVisor does?

• zamalek 6y ago
  So far as WINE is concerned: At the end of the day, x86 is x86. Different operating systems use different loaders/dynamic linkers, different filesystem layouts, different APIs, but still the same machine code and still the same calling conventions. WINE, in a nutshell, merely presents the Windows environment (by wrapping Linux calls in Windows calls) to an executable that is running otherwise natively, there isn't a virtual machine or an emulator involved. There is no sandbox or security (as that is a non-goal). The problem is that various DRM and anti-cheat products use undocumented Windows syscalls to do their job, and syscalls are something that you can't just wrap with a function. This extension will allow WINE to ask Linux to send it unhandled syscalls (via SIGSYS), so that it can emulate them (making it a misnomer for the first time).
  • monocasa 6y ago
    > but still the same machine code and still the same calling conventions. The Linux and Windows calling conventions are pretty different.
    • zamalek 6y ago
      Oof, you're right. Still, it's merely a transition from one convention to another.