linux-kernel - Re: [PATCH v3] vfio-pci: Provide reviewers and acceptance criteria for vendor drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20220317194133.GE11336@nvidia.com>
Date:   Thu, 17 Mar 2022 16:41:33 -0300
From:   Jason Gunthorpe <jgg@...dia.com>
To:     Alex Williamson <alex.williamson@...hat.com>
Cc:     Cornelia Huck <cohuck@...hat.com>, kvm@...r.kernel.org,
        linux-kernel@...r.kernel.org, shameerali.kolothum.thodi@...wei.com,
        kevin.tian@...el.com, yishaih@...dia.com,
        linux-doc@...r.kernel.org, corbet@....net
Subject: Re: [PATCH v3] vfio-pci: Provide reviewers and acceptance criteria
 for vendor drivers

On Tue, Mar 15, 2022 at 10:22:00AM -0600, Alex Williamson wrote:
> On Tue, 15 Mar 2022 12:53:04 -0300

> > 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.
> 
> Are you volunteering to be a reviewer under drivers/vfio/?  Careful,
> I'll add you ;)

Haha, sure you can do that if it helps

We still have a quite a ways to go before all the iommu features are
exposed and we get dirty tracking done.

Thanks,
Jason