Stas Sergeev

I added the patch that is supposed to map it to kvm's phys addr now for real. :)

> So there's a conflict with extmem (if it uses more than 3MB, and mapped at 0x110000 linear) or is this handled > somehow? In devel this is handled by...

Well I guess the easiest solution for now would be for you to just integrate the xms_rv branch into yours, w/o pushing it to devel. This will allow you to...

Hmm, perhaps I've found the simple solution: https://github.com/dosemu2/dosemu2/pull/1881/commits/57c667bf080002ebf1b137a74797c8cf1ac88a61 Why not to just use dpmi_rsv_low as ext_mem?

Except that then we shouldn't write-protect reserved area, so https://github.com/dosemu2/dosemu2/pull/1881/commits/1e62ebffec042890e5587d8d75884ae49736e279

xms_rv built and I think its quite simple to apply to devel. Would you like to check that it actually helps vcpi?

I merged identity mapping for ext_mem, so hope disabling DPMI will not be needed for VCPI.

Oh would you like to complete the simx86 and fpu activities maybe? Why vcpi can't wait? :)

doom is slow and duke is ok even without this patch. vcpi hardly makes a difference here.

So there seems to be some "market" for this actually, eg #875 It is about run286, which would be quite difficult to run on our DPMI impl, even if the...