Re: [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 (was: Re: git-bisect results (was: Re: qemu.git hangs booting Linux after insmod virtio_blk.ko))

[Max Filippov]

>> git bisect says this.  I didn't believe it first time, so I ran it
>> twice with a few modifications, and it pointed to the same commit both
>> times ...
>
> Richard,
> could you please elaborate on your testcase and configuration
> (host/target architecture, command lines, etc).

Ok, I've found most of details, what's not clear to me is how you
decide whether the build is good or bad.

I mean, you need to rebuild qemu on every bisection step, but neither
this commit nor the previous or the next one
change anything that would compile for x86 targets.

>> 67882fd177389527510eb36b3f7712011a835545 is the first bad commit
>> commit 67882fd177389527510eb36b3f7712011a835545
>> Author: Max Filippov <address@hidden>
>> Date:   Tue Sep 6 03:55:28 2011 +0400
>>
>>    target-xtensa: implement narrow instructions
>>
>>    Instructions with op0 >= 8 are 2 bytes long, others are 3 bytes long.
>>
>>    Signed-off-by: Max Filippov <address@hidden>
>>    Signed-off-by: Blue Swirl <address@hidden>
>>
>> Rich.

-- 
Thanks.
-- Max