qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Stefan Haynoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH][v7] megasas: LSI Megaraid SAS emulation
Date: Wed, 20 Jul 2011 08:50:40 +0200	[thread overview]
Message-ID: <4E267AC0.7060307@suse.de> (raw)
In-Reply-To: <20110719160843.GA3414@lst.de>

On 07/19/2011 06:08 PM, Christoph Hellwig wrote:
> I've mentioned this a few times before, but just to make sure it's not
> lost:
>
> This is a really bad idea for adding to qemu.  It's not a controller that
> actually speaks a plain SCSI protocol to disks, but a RAID controller, that
> has it's own command set for data plan operation, and minimal support for
> a few SCSI CDBs around it.  I also supports passthrough channels for
> CDROMs and other periphals, but using those with disks is not recommended
> by LSI, thus explicitly disabled in most drivers and most certainly not
> tested.  So it fits the qemu model, especially if using scsi-generic
> undeneath pretty badly and I don't think it helps us in practice.
>
Hmm. This driver emulates an existing piece of hardware.
If the OS driver has shortcomings, okay, so be it.
But are there any rules which devices might be emulated and which 
shouldn't?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)

  parent reply	other threads:[~2011-07-20  6:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 11:19 [Qemu-devel] [PATCH][v7] megasas: LSI Megaraid SAS emulation Hannes Reinecke
2011-07-19 16:08 ` Christoph Hellwig
2011-07-19 16:39   ` Alexander Graf
2011-07-20  6:50   ` Hannes Reinecke [this message]
2012-01-08 21:56 ` Gerhard Wiesinger
2012-01-09  0:10   ` Andreas Färber

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=4E267AC0.7060307@suse.de \
    --to=hare@suse.de \
    --cc=agraf@suse.de \
    --cc=hch@lst.de \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).