16.04.2012 22:18, Bart Oldeman wrote: > which saved value? > > Anyway there are a few issues for x86-64: > - you can't sigreturn() to DPMI code (i.e., the indirect DPMI switch, > "call sigreturn()" or dropping out of a signal handler), because that > involves calling SYSCALL which destroys %ss. The kernel does not save > and restore %ss (the kernel's sigcontext has no entry for it). Ah, that explains most of everything... :(( Have you considered the $_cpu_emu mode that will emulate v86 and 32bit prot mode with 16bit stack, and nothing more? My guess is that the app does'n work too much with such a setup, so maybe the slowdown will not be big? And 99% of apps will remain completely unaffected.
> When I brought it up several years ago Andi Kleen wasn't very keen to > accept these kind of kernel adjustments... Did you put them to http://v86-64.sourceforge.net/ ? ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
