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
| ||
|
Message-ID: <Y5rE26OcSnoZbqzn@infradead.org> Date: Wed, 14 Dec 2022 22:55:23 -0800 From: Christoph Hellwig <hch@...radead.org> To: 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: [RFC PATCH v2 vfio 0/7] pds vfio driver On Wed, Dec 14, 2022 at 03:21:29PM -0800, Brett Creeley wrote: > This is a first draft patchset for a new vendor specific VFIO driver for > use with the AMD/Pensando Distributed Services Card (DSC). This driver > (pds_vfio) is a client of the newly introduced pds_core driver. Hi Brett, just as said last time and completely ignored by you: any nvme live migration needs to be standardized in the NVMe technical working group before it can be merged in Linux.
Powered by blists - more mailing lists