On 07/31/2012 07:29 PM, Marcelo Tosatti wrote: >> >> So the same problem should happen with %fs and %gs, no? > > AFAICS: > > depends on CONFIG_X86_32_LAZY_GS for GS, unconditional for FS. This fs/gs were already in there, I wonder how it wasn't broken before. Something's fishy here. > >> x86_64 is safe, since it entry_64.S never saves/restores segment registers. > > Is the comment > > /* > * The sysexit path does not restore ds/es, so we must set them > * to > * a reasonable value ourselves. > */ > > Correct? > > syscall_exit -> syscall_exit_work -> resume_userspace -> > restore_all -> RESTORE_REGS > That's the non-sysexit path (could have arrived here by sysenter). Look at sysenter_exit. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
