21.04.2012 16:04, Eric W. Biederman wrote: > Well you could always start a project to write native 16bit programs to But the problem is with the 32bit programs, if they happen to use the 16bit stack for some crazy reason.
> I thought it was an Intel bug? The clever history books say that AMD once bought the right to use Intel's microcode... or something like this. So the old bugs like this are all shared, but then AMD promoted this bug into the 64bit world, so I'd say now this is an AMD bug. There was no reason to carefully adapt this bug for the long mode, but they did so. I mean, now even the 64bit code that happened to use the 32bit stack, will take a crash. > Is it possible you can point me to the errata? I only half understand > what the bug is. Sure: http://www.dosemu.org/docs/EMUfailure/t1.html#AEN54 Please note that any workaround have to be atomic wrt flags handling, esp the TF flag. And any trampoline code in kernel have to be NMI-safe. These 2 conditions got me a hard times in the past. ------------------------------------------------------------------------------ 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
