Re: Wierdness - linux-next KVM patch breaks Dell Latitude D820, KVM not in kernel

[Avi Kivity <avi@redhat.com>]

On 09/09/2009 08:34 PM, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 08 Sep 2009 15:41:28 EDT, Valdis.Kletnieks@vt.edu said:
>
>    
>> Yeah, I was quite confused by the bisect results as well, I may end up
>> re-doing it just to make sure I didn't screw something up along the way (since
>> I started it with -rc7/HEAD as the good/bad, but most of the resulting
>> kernels reported a pre-rc7 release (a 2.6.28 at one point, IIRC, and it
>> finished at 31-rc2.
>>      
> I've become convinced that Something Really Bad happened to the KVM tree in
> linux-next on its way to my laptop - after 2 bisects, it reported I had some
> 2,000 commits left to check.  So I ran 'git bisect visualize' to sanity check.
>
> And *every single one* of those 4,000 commits between 'good' and 'bad' was a
> KVM commit, stretching all the way back to 2007.  Unless that's an artifact
> of the way linux-next is built, I would have expected only "new-ish" commits
> to be in the bisect window, and not just out of one tree...
>
> So I ended up doing a 'WTF?', an 'rm -r', and am cloning over today's linux-next
> and will see if that brings me any better joy.
>
>    

Oh, it's an artifact of kvm.git, not linux-next.  I really should feed 
something better to -next.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.