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
| ||
|
Date: Wed, 2 Feb 2022 13:03:29 -0400 From: Jason Gunthorpe <jgg@...dia.com> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com> Cc: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>, "alex.williamson@...hat.com" <alex.williamson@...hat.com>, "mgurtovoy@...dia.com" <mgurtovoy@...dia.com>, Linuxarm <linuxarm@...wei.com>, liulongfang <liulongfang@...wei.com>, "Zengtao (B)" <prime.zeng@...ilicon.com>, yuzenghui <yuzenghui@...wei.com>, Jonathan Cameron <jonathan.cameron@...wei.com>, "Wangzhou (B)" <wangzhou1@...ilicon.com> Subject: Re: [RFC v2 0/4] vfio/hisilicon: add acc live migration driver On Wed, Feb 02, 2022 at 04:10:06PM +0000, Shameerali Kolothum Thodi wrote: > > > > From: Jason Gunthorpe [mailto:jgg@...dia.com] > > Sent: 02 February 2022 15:40 > > To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com> > > Cc: kvm@...r.kernel.org; linux-kernel@...r.kernel.org; > > linux-crypto@...r.kernel.org; alex.williamson@...hat.com; > > mgurtovoy@...dia.com; Linuxarm <linuxarm@...wei.com>; liulongfang > > <liulongfang@...wei.com>; Zengtao (B) <prime.zeng@...ilicon.com>; > > yuzenghui <yuzenghui@...wei.com>; Jonathan Cameron > > <jonathan.cameron@...wei.com>; Wangzhou (B) <wangzhou1@...ilicon.com> > > Subject: Re: [RFC v2 0/4] vfio/hisilicon: add acc live migration driver > > > > On Wed, Feb 02, 2022 at 02:34:52PM +0000, Shameerali Kolothum Thodi > > wrote: > > > > > > There are few topics to consider: > > > > - Which of the three feature sets (STOP_COPY, P2P and PRECOPY) make > > > > sense for this driver? > > > > > > I think it will be STOP_COPY only for now. We might have PRECOPY > > > feature once we have the SMMUv3 HTTU support in future. > > > > HTTU is the dirty tracking feature? To be clear VFIO migration support for > > PRECOPY has nothing to do with IOMMU based dirty page tracking. > > Yes, it is based on the IOMMU hardware dirty bit management support. > A RFC was posted sometime back, > https://lore.kernel.org/kvm/20210507103608.39440-1-zhukeqian1@huawei.com/ Yes, I saw that. I was hoping to have a discussion on this soon about how to integrate that with the iommufd work, which I hope will allow that series, and the other IOMMU drivers that can support this to be merged.. Jason
Powered by blists - more mailing lists