On 07/03/2012 04:15 PM, Peter Lieven wrote: > On 03.07.2012 15:13, Avi Kivity wrote: >> On 07/03/2012 04:01 PM, Peter Lieven wrote: >>> Further output from my testing. >>> >>> Working: >>> Linux 2.6.38 with included kvm module >>> Linux 3.0.0 with included kvm module >>> >>> Not-Working: >>> Linux 3.2.0 with included kvm module >>> Linux 2.6.28 with kvm-kmod 3.4 >>> Linux 3.0.0 with kvm-kmod 3.4 >>> Linux 3.2.0 with kvm-kmod 3.4 >>> >>> I can trigger the race with any of qemu-kvm 0.12.5, 1.0 or 1.0.1. >>> It might be that the code was introduced somewhere between 3.0.0 >>> and 3.2.0 in the kvm kernel module and that the flaw is not >>> in qemu-kvm. >>> >>> Any hints? >>> >> A bisect could tell us where the problem is. >> >> To avoid bisecting all of linux, try >> >> git bisect v3.2 v3.0 virt/kvm arch/x86/kvm >> >> > would it also be ok to bisect kvm-kmod? Yes, but note that kvm-kmod is spread across two repositories which are not often tested out of sync, so you may get build failures. -- 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
