Skip to contentSkip to conversation

App database, libsynth

DISCUSSION Stas Sergeev 2 participants 2 messages Jul 13, 2003

lore
Share & tools
lore
#0 lore raw

Hello.

Quoted 4 lines · Ryan Underwood
Quoted 1 line

In long mode there is no vm86.

It looked like the long vs legacy mode could be toggled on a per segment basis in the rest of the information I pasted. What do you think that refers to?

That refers to that you seem like confusing the legacy mode with the compatibility mode. See this about switching:
http://www.x86-64.org/lists/discuss/msg03333.html

For now the decision was AFAIK to not mess with vm86() in x86-64 linux port. That may sound sad for us, but I guess they had some reasons for doing so.

#1 lore raw

Hi Stas,

Quoted 11 lines · Stas Sergeev

Hello.

Quoted 4 lines · Ryan Underwood
Quoted 1 line

In long mode there is no vm86.

It looked like the long vs legacy mode could be toggled on a per segment basis in the rest of the information I pasted. What do you think that refers to?

That refers to that you seem like confusing the legacy mode with the compatibility mode. See this about switching:
http://www.x86-64.org/lists/discuss/msg03333.html

Yes, that clears it up. So the legacy mode can only be enabled by rebooting the system since it is too difficult to switch between legacy and longmode on the fly. Furthermore, all the compatibility mode is good for is running 32-bit applications in longmode.

Quoted 4 lines

For now the decision was AFAIK to not mess with vm86() in x86-64 linux port. That may sound sad for us, but I guess they had some reasons for doing so.

I think most people will be using longmode on AMD-64 anyhow, so we should get the fast CPU emulation going as soon as possible.

Side effect of the CPU emulation : can we do things with it like run Win95 or other VCPI program underneath DOSEMU?

Signature · 1 line
Ryan Underwood, <nemesis at icequake.net>, icq=10317253