Re:Linux as co-operative Windows process
by quotemstr on Sunday February 09, 2025 @11:59AM
(#42991846)
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.
[ Parent
| on HN ]
Re:Linux as co-operative Windows process
by badc0ffee on Sunday February 09, 2025 @12:09PM
(#42991905)
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.
Re:Linux as co-operative Windows process
by lproven on Monday February 10, 2025 @01:39PM
(#43003575)
AIUI this is correct, yes.
Re:Linux as co-operative Windows process
by quotemstr on Monday February 10, 2025 @08:24PM
(#43007809)
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.
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#/me...
