On 02/21/2012 11:41 PM, Linus Torvalds wrote: > Btw, I really don't like what arch/x86/kvm/ does with CR0.TS and the FP > state. I'm not at all sure that's all kosher. But I don't know the > code, so I just made sure that at no point did any of the semantics > change. > Can you elaborate on what you don't like in the kvm code (apart from "it does virtualiztion")? btw, some time ago I did some work to lazify fpu save (as opposed to just fpu restore) and abstract out the various users (user mode, kernel threads, irq context, guest mode, and signal handlers). This would allow you to run task A's user mode with task B's fpu loaded, have preemptible kernel fpu being, avoid fpu switching while handling signals, and run user mode with a guest fpu loaded or vice versa. However I abandoned the effort as too complex. Perhaps a more determined hacker can make more progress there. -- 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
