4 ms·

The site is down, so I can't see what they're doing with the MMU: that said, most virtual memory management works just fine from normal boring userspace. If win

The site is down, so I can't see what they're doing with the MMU: that said, most virtual memory management works just fine from normal boring userspace. If wine can do it for running win32 on Linux, this thing can do it for running Linux stuff on win32, which isn't less powerful when it comes to virtual memory management.

badc0ffee 2y ago
It's been years since I used Wine, but I think it just runs each Windows process in its own Linux process. There's no Wine "kernel" that needs to manage virtual memory or isolate multiple processes.
- lproven 2y ago
  AIUI this is correct, yes.
  - quotemstr 2y ago
    Sort of. Wine still has a privileged (w.r.t. other wine processes) manager process that handles coordination between other wine processes. Whether that's a "kernel" is a matter of opinion.
p_ing 2y ago
The VMM is part of the kernel (or executive), not userspace. App requests memory, VMM assigns pages from RAM, page file, or backing store. If you wanted to segment yourself and take over anything 'below' the kernel like the MMU, you'd need elevated rights. But that'd be some interesting programming. https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/media/File:Windows_2000_architecture.svg https://en.wikipedia.org/wiki/Architecture_of_Windows_NT#/me...
- quotemstr 2y ago
  Huh? What are you talking about? I can manipulate page tables just fine from userspace through the magic of MapViewOfFile.