On Tuesday 06 March 2007 00:10, Jeff Dike wrote: > On Tue, Mar 06, 2007 at 12:03:26AM +0100, Blaisorblade wrote: > > > No, RCX corruption is different - that happens when a sysexit is done > > > from a system call where userspace wasn't prepared to save and restore > > > RCX. sigreturn is the best example.
> > Hmm... we should finally fix that, at some point. Or... now that you > > explain it this way, it could even seem unfixable... is it? Or maybe > > sysreturn should become a syscall where the return must happen through > > the slow return path (iret), if that exists for x86_64. > This is fixed, and has been for a while. The fix was, as you suggest, > return through iret in this case. Also the 32bit emulation case? That would be interesting for SKAS with 64bit host and 32bit guest (which I haven't tested for a long time). Also this means that I could test the needed trivial fixes for 64 on 64 (like opening /proc/mm64, using PTRACE_EX_FAULTINFO which I introduced...). -- Inform me of my mistakes, so I can add them to my list! Paolo Giarrusso, aka Blaisorblade http://www.user-mode-linux.org/~blaisorblade Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
