On 05/11/2015 17:15, Paolo Bonzini wrote: > > > On 05/11/2015 17:07, Gerhard Wiesinger wrote: >>> >> >> ./trace-cmd record -b 20000 -e kvm >> ./trace-cmd report | grep -i task_switch >> qemu-system-x86-6024 [001] 792774.719297: kvm_exit: reason task_switch >> rip 0x4883 info 158 4000000000 > > 0x158 is the segment selector of the incoming TSS, and the task switch > was caused by a far jump. > >> But I can't interpret it. > > Neither can I; you have to send the whole trace. > >> But I know my patch works well. Since it is >> just a module parameter it is fully backward compatible by default and >> because of the one liner no side effects are possible. So a intergration >> would be good. > > It's also papering over a bug, and likely the bug still triggers on > Intel systems. So it's not acceptable. > > Can you provide reproduction instructions please? At the very least, does it reproduce without KVM? Paolo -- 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
