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] [thread-next>] [day] [month] [year] [list]
Message-ID: <4220d8d7-1140-9570-3d6c-ba70c4048d98@amd.com>
Date:   Mon, 20 Feb 2023 16:45:51 -0800
From:   Brett Creeley <bcreeley@....com>
To:     Christoph Hellwig <hch@...radead.org>,
        Brett Creeley <brett.creeley@....com>
Cc:     kvm@...r.kernel.org, netdev@...r.kernel.org,
        alex.williamson@...hat.com, cohuck@...hat.com, jgg@...dia.com,
        yishaih@...dia.com, shameerali.kolothum.thodi@...wei.com,
        kevin.tian@...el.com, shannon.nelson@....com, drivers@...sando.io
Subject: Re: [PATCH v3 vfio 0/7] pds vfio driver

On 2/19/2023 10:29 PM, Christoph Hellwig wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> 
> 
> On Sun, Feb 19, 2023 at 12:39:01AM -0800, Brett Creeley wrote:
>> This is a draft patchset for a new vendor specific VFIO driver
>> (pds_vfio) for use with the AMD/Pensando Distributed Services Card
>> (DSC). This driver is device type agnostic and live migration is
>> supported as long as the underlying SR-IOV VF supports live migration
>> on the DSC. This driver is a client of the newly introduced pds_core
>> driver, which the latest version can be referenced at:
> 
> Just as a broken clock:  non-standard nvme live migration is not
> acceptable.  Please work with the NVMe technical workning group to
> get this feature standardized.  Note that despite various interested
> parties on linux lists I've seen exactly zero activity from the
> (not so) smart nic vendors active there.


You're right, we intend to work with the respective groups, and we 
removed any mention of NVMe from the series. However, this solution 
applies to our other PCI devices.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ