From: Anthony Liguori <anthony@codemonkey.ws>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Max Filippov <jcmvbkbc@gmail.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 (was: Re: git-bisect results
Date: Fri, 16 Dec 2011 19:39:48 -0600 [thread overview]
Message-ID: <4EEBF2E4.6000807@codemonkey.ws> (raw)
In-Reply-To: <20111217000704.GB23695@amd.home.annexia.org>
On 12/16/2011 06:07 PM, Richard W.M. Jones wrote:
>
> 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 ...
Need more details because it doesn't appear to be broken to me.
What guest, what's your command line, what guest kernel version, how does it
break, etc..
Regards,
Anthony Liguori
>
> 67882fd177389527510eb36b3f7712011a835545 is the first bad commit
> commit 67882fd177389527510eb36b3f7712011a835545
> Author: Max Filippov<jcmvbkbc@gmail.com>
> 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<jcmvbkbc@gmail.com>
> Signed-off-by: Blue Swirl<blauwirbel@gmail.com>
>
> Rich.
>
next prev parent reply other threads:[~2011-12-17 1:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 13:11 [Qemu-devel] qemu.git hangs booting Linux after insmod virtio_blk.ko Richard W.M. Jones
2011-09-30 16:51 ` [Qemu-devel] git-bisect results (was: Re: qemu.git hangs booting Linux after insmod virtio_blk.ko) Richard W.M. Jones
2011-12-16 22:19 ` Richard W.M. Jones
2011-12-17 0:07 ` [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)) Richard W.M. Jones
2011-12-17 0:26 ` Max Filippov
2011-12-17 0:53 ` Max Filippov
2011-12-17 1:44 ` [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 (was: Re: git-bisect results Anthony Liguori
2011-12-17 8:33 ` Richard W.M. Jones
2011-12-17 15:13 ` [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 Anthony Liguori
2011-12-17 15:22 ` Richard W.M. Jones
2011-12-17 15:22 ` Anthony Liguori
2011-12-17 15:25 ` Richard W.M. Jones
2011-12-17 16:24 ` Anthony Liguori
2011-12-17 16:35 ` Richard W.M. Jones
2011-12-17 16:49 ` Kevin O'Connor
2011-12-17 17:03 ` Anthony Liguori
2011-12-17 17:30 ` Richard W.M. Jones
2011-12-19 10:31 ` Daniel P. Berrange
2011-12-19 17:23 ` [Qemu-devel] [SeaBIOS] " Fred .
2011-12-19 17:26 ` Fred .
2011-12-19 17:34 ` [Qemu-devel] " Anthony Liguori
2011-12-19 17:43 ` Daniel P. Berrange
2011-12-19 18:02 ` Anthony Liguori
2011-12-19 19:04 ` Richard W.M. Jones
2011-12-19 19:16 ` Daniel P. Berrange
2011-12-19 19:40 ` Richard W.M. Jones
2011-12-19 19:42 ` Richard W.M. Jones
2011-12-19 19:44 ` Anthony Liguori
2011-12-19 19:19 ` Daniel P. Berrange
2011-12-19 19:26 ` Anthony Liguori
2011-12-20 3:38 ` Kevin O'Connor
2011-12-20 8:13 ` Gleb Natapov
2011-12-17 13:16 ` [Qemu-devel] insmod virtio-blk is broken in qemu 1.0 (was: Re: git-bisect results Richard W.M. Jones
2011-12-17 1:39 ` Anthony Liguori [this message]
2011-12-17 1:43 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EEBF2E4.6000807@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jcmvbkbc@gmail.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).