linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com,
	yishaih@nvidia.com, linux-doc@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH v3] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers
Date: Tue, 15 Mar 2022 12:53:04 -0300	[thread overview]
Message-ID: <20220315155304.GC11336@nvidia.com> (raw)
In-Reply-To: <87a6drh8hy.fsf@redhat.com>

On Tue, Mar 15, 2022 at 10:26:17AM +0100, Cornelia Huck wrote:
> On Mon, Mar 14 2022, Alex Williamson <alex.williamson@redhat.com> wrote:
> 
> > Vendor or device specific extensions for devices exposed to userspace
> > through the vfio-pci-core library open both new functionality and new
> > risks.  Here we attempt to provided formalized requirements and
> > expectations to ensure that future drivers both collaborate in their
> > interaction with existing host drivers, as well as receive additional
> > reviews from community members with experience in this area.
> >
> > Cc: Jason Gunthorpe <jgg@nvidia.com>
> > Cc: Yishai Hadas <yishaih@nvidia.com>
> > Cc: Kevin Tian <kevin.tian@intel.com>
> > Acked-by: Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
> > Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> 
> (...)
> 
> > diff --git a/Documentation/driver-api/vfio-pci-vendor-driver-acceptance.rst b/Documentation/driver-api/vfio-pci-vendor-driver-acceptance.rst
> > new file mode 100644
> > index 000000000000..3a108d748681
> > +++ b/Documentation/driver-api/vfio-pci-vendor-driver-acceptance.rst
> 
> What about Christoph's request to drop the "vendor" name?
> vfio-pci-device-specific-driver-acceptance.rst would match the actual
> title of the document, and the only drawback I see is that it is a bit
> longer.

I agree we should not use the vendor name

In general I wonder if this is a bit too specific to PCI, really this
is just review criteria for any driver making a struct vfio_device_ops
implementation, and we have some specific guidance for migration here
as well.

Like if IBM makes s390 migration drivers all of this applies just as
well even though they are not PCI.

> > +New driver submissions are therefore requested to have approval via
> > +Sign-off/Acked-by/etc for any interactions with parent drivers.
> 
> s/Sign-off/Reviewed-by/ ?
> 
> I would not generally expect the reviewers listed to sign off on other
> people's patches.

It happens quite a lot when those people help write the patches too :)

Jason

  reply	other threads:[~2022-03-15 15:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 20:24 [PATCH v3] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers Alex Williamson
2022-03-15  2:14 ` Tian, Kevin
2022-03-15  7:23 ` Yishai Hadas
2022-03-15  9:26 ` Cornelia Huck
2022-03-15 15:53   ` Jason Gunthorpe [this message]
2022-03-15 16:22     ` Alex Williamson
2022-03-15 17:32       ` Cornelia Huck
2022-03-17 19:41       ` Jason Gunthorpe

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=20220315155304.GC11336@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=corbet@lwn.net \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=yishaih@nvidia.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).