public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: James Bottomley <jejb@linux.ibm.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	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, 7 Dec 2022 17:01:40 +0100	[thread overview]
Message-ID: <20221207160140.ilh63xxxgefs5hff@sirius.home.kraxel.org> (raw)
In-Reply-To: <887bc678bbd4a356edd420809bffa0964e0b162b.camel@linux.ibm.com>

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.

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.

> On the other hand, I've got to say I use virtio-scsi in all
> my VM testing environments,

Same here ;)

take care,
  Gerd


  reply	other threads:[~2022-12-07 16:02 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 [this message]
2022-12-07 16:04                   ` Ard Biesheuvel
2022-12-07 16:22                     ` James Bottomley
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=20221207160140.ilh63xxxgefs5hff@sirius.home.kraxel.org \
    --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