From: Hannes Reinecke <hare@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
kraxel@redhat.com, qemu-devel@nongnu.org, nab@linux-iscsi.org,
stefanha@gmail.com
Subject: Re: [Qemu-devel] [PATCH 16/16] megasas: LSI Megaraid SAS emulation
Date: Fri, 19 Nov 2010 15:19:23 +0100 [thread overview]
Message-ID: <4CE6876B.9010001@suse.de> (raw)
In-Reply-To: <m3lj4pl86o.fsf@blackfin.pond.sub.org>
On 11/19/2010 03:06 PM, Markus Armbruster wrote:
> Jes Sorensen <Jes.Sorensen@redhat.com> writes:
>
>> On 11/18/10 15:47, Hannes Reinecke wrote:
>>> This patch adds an emulation for the LSI Megaraid SAS HBA.
>>>
>>> Signed-off-by: Hannes Reinecke <hare@suse.de>
>>> ---
>>> Makefile.objs | 2 +-
>>> hw/megasas.c | 1826 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> hw/mfi.h | 1197 +++++++++++++++++++++++++++++++++++++
>>> hw/pci_ids.h | 2 +
>>> hw/scsi.h | 1 +
>>> 5 files changed, 3027 insertions(+), 1 deletions(-)
>>> create mode 100644 hw/megasas.c
>>> create mode 100644 hw/mfi.h
>>>
>>> diff --git a/Makefile.objs b/Makefile.objs
>>> index 15569af..54c6e02 100644
>>> --- a/Makefile.objs
>>> +++ b/Makefile.objs
>>> @@ -231,7 +231,7 @@ hw-obj-$(CONFIG_IDE_MACIO) += ide/macio.o
>>> hw-obj-$(CONFIG_IDE_VIA) += ide/via.o
>>>
>>> # SCSI layer
>>> -hw-obj-y += lsi53c895a.o
>>> +hw-obj-y += lsi53c895a.o megasas.o
>>> hw-obj-$(CONFIG_ESP) += esp.o
>>>
>>> hw-obj-y += dma-helpers.o sysbus.o isa-bus.o
>>
>> Just had a look through your patches and have to say nice work. Haven't
>> tested it though, but looks like a good step in the right direction.
>>
>> Only comment, as you are adding another SCSI driver, maybe it's time to
>> make the driver selection configurable, rather than hard coding the build?
>
> What do you mean by that?
>
> We hardcode lsi53c895a in two places where we really mean "default SCSI
> controller type": pc_pci_device_init(), which applies to "-drive
> if=scsi", and qemu_pci_hot_add_storage(), which applies to "pci_add
> storage if=scsi". Not sure making that default configurable is worth
> it.
>
> If you want more control than -drive and pci_add provice, use -device
> and device_add.
Idea is probably to have megasas the default SCSI controller, if
configured during compile time. Basically have a configure option
'--scsi-hba=megasas' or somesuch.
But then, you can 'easily' select the megasas HBA nowadays with
-drive file=XXX,if=none,id=d1 \
-device megasas,id=m1 \
-device scsi-disk,drive=d1
So not sure if it's worthwhile.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2010-11-19 14:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 14:47 [Qemu-devel] [PATCH 16/16] megasas: LSI Megaraid SAS emulation Hannes Reinecke
2010-11-19 9:20 ` Jes Sorensen
2010-11-19 14:06 ` Markus Armbruster
2010-11-19 14:19 ` Hannes Reinecke [this message]
2010-11-19 14:31 ` Jes Sorensen
2010-11-19 16:36 ` Alexander Graf
2010-11-19 17:35 ` Jes Sorensen
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=4CE6876B.9010001@suse.de \
--to=hare@suse.de \
--cc=Jes.Sorensen@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.com \
--cc=nab@linux-iscsi.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).