Hi, 17.04.2012 04:39, Bart Oldeman wrote: > On 16 April 2012 17:30, Stas Sergeevwrote: >> 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. > It's certainly a possibility though not super easy. I would even claim this is a good candidate for the default setting.
>>> When I brought it up several years ago Andi Kleen wasn't very keen to >>> accept these kind of kernel adjustments... Andi Kleen was saying about a 16bit code workarounds. Do you know what does he mean? Even if he meant the 32bit code (I don't see the problem with 16bit code), then maybe the %ss saving on signal does not fall into that category? >> Did you put them to >> http://v86-64.sourceforge.net/ >> ? > No, I just knew they existed for x86-32 and was enquiring whether they > would be accepted in the first place. I think we can always ask to put such a patches into http://v86-64.sourceforge.net and then see. > I put up a git repository that is a mirror of the svn: > git clone git://dosemu.git.sourceforge.net/gitroot/dosemu/dosemu > > hope that helps, It surely will! :) ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Dosemu-devel mailing list Dosemu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dosemu-devel
