From: Avi Kivity <avi@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [PATCH 0/4] megaraid_sas HBA emulation
Date: Wed, 28 Oct 2009 10:20:00 +0200 [thread overview]
Message-ID: <4AE7FEB0.6000207@redhat.com> (raw)
In-Reply-To: <20091028091129.n46xqd1lww8oosc8@imap.suse.de>
On 10/28/2009 10:11 AM, Hannes Reinecke wrote:
>
> The problem is I don't have any documentation for the LSI parallel
> SCSI controller. So I don't know if and in what shape I/O is passed
> down, nor anything else. And as the SCSI disk emulation is really
> tied into the LSI parallel SCSI controller, any change in the former
> is likely to break the latter.
> And what with me no way of fixing it. Hence I decided on this approach.
>
> I surely can go ahead and patch up the scsi disk emulation, but it's
> quite likely to break the LSI controller. If that's okay with everybody,
> I'll surely go ahead there.
Reverse engineered devices are dangerous. They might work on some
guests but break badly on others, or even worse, break when a guest
driver is updated.
Is there no way to get the documentation?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Hannes Reinecke <hare@suse.de>
Cc: virtualization@lists.linux-foundation.org,
Gerd Hoffmann <kraxel@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] megaraid_sas HBA emulation
Date: Wed, 28 Oct 2009 10:20:00 +0200 [thread overview]
Message-ID: <4AE7FEB0.6000207@redhat.com> (raw)
In-Reply-To: <20091028091129.n46xqd1lww8oosc8@imap.suse.de>
On 10/28/2009 10:11 AM, Hannes Reinecke wrote:
>
> The problem is I don't have any documentation for the LSI parallel
> SCSI controller. So I don't know if and in what shape I/O is passed
> down, nor anything else. And as the SCSI disk emulation is really
> tied into the LSI parallel SCSI controller, any change in the former
> is likely to break the latter.
> And what with me no way of fixing it. Hence I decided on this approach.
>
> I surely can go ahead and patch up the scsi disk emulation, but it's
> quite likely to break the LSI controller. If that's okay with everybody,
> I'll surely go ahead there.
Reverse engineered devices are dangerous. They might work on some
guests but break badly on others, or even worse, break when a guest
driver is updated.
Is there no way to get the documentation?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-28 8:20 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 15:26 [PATCH 0/4] megaraid_sas HBA emulation Hannes Reinecke
2009-10-27 15:26 ` [Qemu-devel] " Hannes Reinecke
2009-10-27 16:47 ` Gerd Hoffmann
2009-10-27 16:47 ` Gerd Hoffmann
2009-10-28 8:11 ` Hannes Reinecke
2009-10-28 8:11 ` Hannes Reinecke
2009-10-28 8:11 ` Hannes Reinecke
2009-10-28 8:20 ` Avi Kivity [this message]
2009-10-28 8:20 ` Avi Kivity
2009-10-28 8:20 ` Avi Kivity
2009-10-28 8:40 ` Christoph Hellwig
2009-10-28 8:40 ` Christoph Hellwig
2009-10-28 8:40 ` Christoph Hellwig
2009-10-28 10:54 ` Gerd Hoffmann
2009-10-28 10:54 ` Gerd Hoffmann
2009-10-28 10:54 ` Gerd Hoffmann
2009-10-28 13:58 ` Gerd Hoffmann
2009-10-28 13:58 ` Gerd Hoffmann
2009-10-28 19:25 ` Hannes Reinecke
2009-10-28 19:25 ` Hannes Reinecke
2009-10-29 4:37 ` Christoph Hellwig
2009-10-29 4:37 ` Christoph Hellwig
2009-10-29 8:47 ` Gerd Hoffmann
2009-10-29 8:47 ` Gerd Hoffmann
2009-10-29 8:47 ` Gerd Hoffmann
2009-10-29 12:57 ` Gerd Hoffmann
2009-10-29 12:57 ` Gerd Hoffmann
2009-10-29 14:57 ` Christoph Hellwig
2009-10-29 14:57 ` Christoph Hellwig
2009-10-29 14:57 ` Christoph Hellwig
2009-10-29 15:14 ` Anthony Liguori
2009-10-29 15:14 ` Anthony Liguori
2009-10-29 15:15 ` Christoph Hellwig
2009-10-29 15:15 ` Christoph Hellwig
2009-10-29 15:25 ` Anthony Liguori
2009-10-29 15:25 ` Anthony Liguori
2009-10-30 8:55 ` Gerd Hoffmann
2009-10-30 8:55 ` Gerd Hoffmann
2009-10-30 8:55 ` Gerd Hoffmann
2009-10-29 15:25 ` Anthony Liguori
2009-10-29 15:15 ` Christoph Hellwig
2009-10-29 15:14 ` Anthony Liguori
2009-10-30 8:12 ` Hannes Reinecke
2009-10-30 8:12 ` Hannes Reinecke
2009-11-03 21:03 ` Gerd Hoffmann
2009-11-03 21:03 ` Gerd Hoffmann
2009-11-03 21:03 ` Gerd Hoffmann
2009-10-30 8:12 ` Hannes Reinecke
2009-10-29 12:57 ` Gerd Hoffmann
2009-10-29 4:37 ` Christoph Hellwig
2009-10-27 16:47 ` Gerd Hoffmann
2009-11-11 1:49 ` Paul Brook
2009-11-11 1:49 ` Paul Brook
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=4AE7FEB0.6000207@redhat.com \
--to=avi@redhat.com \
--cc=hare@suse.de \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.