From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] [PATCH 0/4] megaraid_sas HBA emulation Date: Wed, 28 Oct 2009 10:20:00 +0200 Message-ID: <4AE7FEB0.6000207@redhat.com> References: <4AE71116.6080809@suse.de> <4AE72419.60608@redhat.com> <20091028091129.n46xqd1lww8oosc8@imap.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Gerd Hoffmann , kvm@vger.kernel.org, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org To: Hannes Reinecke Return-path: Received: from mx1.redhat.com ([209.132.183.28]:58903 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932652AbZJ1IUd (ORCPT ); Wed, 28 Oct 2009 04:20:33 -0400 In-Reply-To: <20091028091129.n46xqd1lww8oosc8@imap.suse.de> Sender: kvm-owner@vger.kernel.org List-ID: 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. From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N33lq-0002Vw-6g for qemu-devel@nongnu.org; Wed, 28 Oct 2009 04:20:42 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N33lk-0002Sv-PS for qemu-devel@nongnu.org; Wed, 28 Oct 2009 04:20:41 -0400 Received: from [199.232.76.173] (port=49304 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N33lk-0002Ss-L3 for qemu-devel@nongnu.org; Wed, 28 Oct 2009 04:20:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:16757) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N33lk-00072u-8y for qemu-devel@nongnu.org; Wed, 28 Oct 2009 04:20:36 -0400 Message-ID: <4AE7FEB0.6000207@redhat.com> Date: Wed, 28 Oct 2009 10:20:00 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 0/4] megaraid_sas HBA emulation References: <4AE71116.6080809@suse.de> <4AE72419.60608@redhat.com> <20091028091129.n46xqd1lww8oosc8@imap.suse.de> In-Reply-To: <20091028091129.n46xqd1lww8oosc8@imap.suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Hannes Reinecke Cc: virtualization@lists.linux-foundation.org, Gerd Hoffmann , kvm@vger.kernel.org, qemu-devel@nongnu.org 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.