From: Paolo Bonzini <pbonzini@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] scsi: lsi problems since "unit attention on reset"
Date: Mon, 26 Sep 2011 17:22:35 +0200 [thread overview]
Message-ID: <4E8098BB.4060103@redhat.com> (raw)
In-Reply-To: <4E809603.4000100@siemens.com>
On 09/26/2011 05:10 PM, Jan Kiszka wrote:
> And you were right: it turned out to be a driver issue. The bug sneaked
> in while adapting the original driver to some specific differences
> between QEMU and real HW (here: lacking compat bit support).
Cool, then we can leave in the patch I think. I originally did it in
hope of detecting possible bugs with (upcoming) migration support, which
will use unit attention to make the guest requeue all requests on the
destination. It looks like my goal has been attained.
Out of curiosity, have you ever looked into (or are you interested into)
using multiple LUNs per target with the LSI driver? It crashes
miserably for me with a page fault in the Linux ISR, and that's when I
started using another device. :)
You can play with them on the scsi-addr branch of
git://github.com/bonzini/qemu.git; just create two scsi-disk devices,
with lun=0 and lun=1, and they will get the same target ID but two
different LUNs. It's of course possible the bug is in my code, but then
I got the same failure with two completely different implementations of
the feature so...
Paolo
next prev parent reply other threads:[~2011-09-26 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 7:27 [Qemu-devel] scsi: lsi problems since "unit attention on reset" Jan Kiszka
2011-09-26 7:50 ` Paolo Bonzini
2011-09-26 9:23 ` Jan Kiszka
2011-09-26 9:49 ` Paolo Bonzini
2011-09-26 10:26 ` Jan Kiszka
2011-09-26 11:00 ` Paolo Bonzini
2011-09-26 15:10 ` Jan Kiszka
2011-09-26 15:22 ` Paolo Bonzini [this message]
2011-09-26 16:12 ` Jan Kiszka
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=4E8098BB.4060103@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
/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).