public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "James Bottomley" <jejb@linux.ibm.com>
To: Ard Biesheuvel <ardb@kernel.org>, Gerd Hoffmann <kraxel@redhat.com>
Cc: Mike Maslenkin <mike.maslenkin@gmail.com>,
	devel@edk2.groups.io, dann.frazier@canonical.com,
	michael.d.kinney@intel.com,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	Jordan Justen <jordan.l.justen@intel.com>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	Erdem Aktas <erdemaktas@google.com>, Min Xu <min.m.xu@intel.com>,
	Tom Lendacky <thomas.lendacky@amd.com>,
	1016359@bugs.debian.org
Subject: Re: [edk2-devel] [Patch 1/2] OvmfPkg: Change default to disable MptScsi and PvScsi
Date: Wed, 07 Dec 2022 11:22:10 -0500	[thread overview]
Message-ID: <9365af87923dc2dd59b7cd6aa59e1fba33f4bb5a.camel@linux.ibm.com> (raw)
In-Reply-To: <CAMj1kXF_8Qpp_KCS1aUX2urjYwHZgiGCOtQw0UM3sgvwsPC9YQ@mail.gmail.com>

On Wed, 2022-12-07 at 17:04 +0100, Ard Biesheuvel wrote:
> On Wed, 7 Dec 2022 at 17:02, Gerd Hoffmann <kraxel@redhat.com> wrote:
> > 
> > On Wed, Dec 07, 2022 at 09:14:39AM -0500, James Bottomley wrote:
> > > On Wed, 2022-12-07 at 15:09 +0100, Ard Biesheuvel wrote:
> > > > So at some point, these drivers will be removed rather than
> > > > kept
> > > > alive by the core team unless someone steps up.
> > > 
> > > How important is keeping them alive?
> > 
> > Most common use case is probably bootimg images created on other
> > hypervisors on qemu.  Otherwise there is little reason to use
> > something which is not virtio-scsi.
> > 
> > > I can volunteer to "maintain" them which I anticipate won't be
> > > much effort (plus I'm used to looking after obsolete SCSI
> > > equipment).  The hardware is obsolete, so the mechanics of their
> > > emulation isn't going to change, the only potential risk is
> > > changes in the guest to host transmission layer that breaks
> > > something.
> > 
> 
> Thanks James, that would be very helpful.
> 
> > Yes, I don't expect it being much effort, but knowing oldish scsi
> > stuff certainly helps understanding the driver code if needed.  If
> > you want step up sent a patch updating Maintainers.txt accordingly.
> > 
> 
> Having the informed opinion of a domain expert should allow us to
> diagnose issued related to these drivers with more confidence, and
> also give us insight in how obsolete those drivers actually are.
> 
> I can send the patch if you prefer.

Sure, who can resist someone else doing all the work.

I note we do have a maintained LSI driver: OvmfPkg/LsiScsiDxe.  It
seems to be based on the 53c896 which is really only a marginal subset
of the 1030 ... if I'm remembering correctly the 1030 did Low Voltage
Differential (so a faster SCSI Parallel bus), but since that's a SCSI
Bus protocol, it should have no real impact on the utility of the
emulation.  Is the LsiScsiDxe usable by Debian?

James


  reply	other threads:[~2022-12-07 16:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 19:46 [Patch 0/2] Remove MptScsi and PvScsi reviewers Michael D Kinney
2022-07-26 19:46 ` [Patch 1/2] OvmfPkg: Change default to disable MptScsi and PvScsi Michael D Kinney
2022-12-05 23:36   ` [edk2-devel] " dann frazier
2022-12-06  1:25     ` Michael D Kinney
2022-12-06  2:07       ` dann frazier
2022-12-06  5:56     ` Gerd Hoffmann
2022-12-06 14:37       ` dann frazier
2022-12-06 14:55         ` Mike Maslenkin
2022-12-07  7:41           ` Gerd Hoffmann
2022-12-07 14:09             ` Ard Biesheuvel
2022-12-07 14:14               ` James Bottomley
2022-12-07 16:01                 ` Gerd Hoffmann
2022-12-07 16:04                   ` Ard Biesheuvel
2022-12-07 16:22                     ` James Bottomley [this message]
2022-12-07 21:59                       ` dann frazier
2022-07-26 19:46 ` [Patch 2/2] Maintainers.txt: Remove MptScsi and PvScsi reviewers Michael D Kinney
2022-07-26 20:39 ` [Patch 0/2] " Ard Biesheuvel
2022-07-27  0:38 ` Yao, Jiewen
2022-08-15 15:00 ` Gerd Hoffmann

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=9365af87923dc2dd59b7cd6aa59e1fba33f4bb5a.camel@linux.ibm.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