From: "Laszlo Ersek" <lersek@redhat.com>
To: Gary Lin <glin@suse.com>
Cc: devel@edk2.groups.io, Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [RFC PATCH 1/1] OvmfPkg: Introduce LSI 53C895A SCSI Controller Driver
Date: Wed, 17 Jun 2020 12:38:34 +0200 [thread overview]
Message-ID: <99277128-7971-0a92-047b-1c4338afdad5@redhat.com> (raw)
In-Reply-To: <20200617020908.GC18504@GaryWorkstation>
On 06/17/20 04:09, Gary Lin wrote:
> On Mon, Jun 15, 2020 at 01:27:22PM +0200, Laszlo Ersek wrote:
>> Hello Gary,
>>
> Hi Laszlo,
>
>> On 06/12/20 12:04, Gary Lin wrote:
>>> This commit introduces the driver for LSI 53C895A SCSI Controller
>>> which, so that OVMF can access the devices attached to the emulated
>>> "lsi" SCSI controller.
>>>
>>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>>> Cc: Laszlo Ersek <lersek@redhat.com>
>>> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
>>> Signed-off-by: Gary Lin <glin@suse.com>
>>> ---
>>> Although lsi is now considered obsolete in QEMU, I wrote this driver
>>> mainly for learning the UEFI SCSI driver and ... FUN! The majority of
>>> the code is actually borrowed from VirtioScsci and MptScsi, and I
>>> mainly focus on LsiScsiPassThru().
>>>
>>> If it's fine to add this driver into OvmfPkg, I'll start to split this
>>> patch into smaller pieces to make it easier to review.
>>
>> (1) Do we have an official deprecation notice for this SCSI controller
>> in QEMU?
>>
>> If we do, then (AIUI) the controller will be removed in QEMU in one or
>> two releases, so this code would become effectively dead in the mid
>> term. I wouldn't like to review and/or carry code that's soon to be
>> dead.
>>
> I just vaguely remember that virtio-scsi is the new default over lsi and
> it's not recommended to use lsi except for the old OS without virtio-scsi
> driver.
So the question is then whether the old OS that supports LSI but not
virtio-scsi is capable of booting on UEFI in the first place.
>
>> (2) If there is no official deprecation notice in QEMU, then I agree it
>> makes sense to include this driver. In that case, I have another
>> question:
>>
>> Do you intend this driver for production purposes? I.e., do you expect
>> users or "layered products" (libvirt, proxmox, openstack, ...) to use
>> this SCSI controller for some well-defined purpose? (The MPT SCSI and PV
>> SCSI drivers had a clear product-oriented modivation:
>>
>> https://edk2.groups.io/g/devel/message/55620
>> http://mid.mail-archive.com/a96b6b74-c35d-e291-2122-9d77f1d5f89c@oracle.com
>> )
>>
>> (2a) If this driver is not meant for a production environment, then
>> LSI_SCSI_ENABLE should be FALSE by default (and I'll do a lighter
>> review).
>>
>> (2b) If the driver is meant for production, then LSI_SCSI_ENABLE should
>> indeed be TRUE, and I'll have to be more diligent in reviewing this.
>>
> I kind of wonder if the any serious use for lsi+ovmf. If the OS is so
> old and only supports lsi, seabios probably serves it better.
Right, my point exactly!
> Anyway,
> I'll try to gather more information from my colleagues to see if they
> got any feedback about lsi from our customers. If not, I'll set
> LSI_SCSI_ENABLE to FALSE by default.
Sounds like a good approach!
>
>> For either (2a) or (2b), please do split up the driver into smaller
>> patches, and please also add yourself to Maintainers.txt as the
>> designated reviewer of the new driver.
>>
> Sure. Will do that.
Thanks!
Laszlo
prev parent reply other threads:[~2020-06-17 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 10:04 [RFC PATCH 1/1] OvmfPkg: Introduce LSI 53C895A SCSI Controller Driver Gary Lin
2020-06-15 11:27 ` Laszlo Ersek
2020-06-17 2:09 ` Gary Lin
2020-06-17 10:38 ` Laszlo Ersek [this message]
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-list 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=99277128-7971-0a92-047b-1c4338afdad5@redhat.com \
--to=devel@edk2.groups.io \
/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