mbox series

[v2,0/3] update live migration configuration region

Message ID 20250304120528.63605-1-liulongfang@huawei.com (mailing list archive)
Headers show
Series update live migration configuration region | expand

Message

Longfang Liu March 4, 2025, 12:05 p.m. UTC 
On the new hardware platform, the configuration register space
of the live migration function is set on the PF, while on the
old platform, this part is placed on the VF.

Change v1 -> v2
	Delete the vf_qm_state read operation in Pre_Copy

Longfang Liu (3):
  migration: update BAR space size
  migration: qm updates BAR configuration
  migration: adapt to new migration configuration

 drivers/crypto/hisilicon/qm.c                 |  28 +++
 .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    | 224 ++++++++++++------
 .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h    |   7 +
 3 files changed, 190 insertions(+), 69 deletions(-)

Comments

Shameerali Kolothum Thodi March 4, 2025, 12:26 p.m. UTC | #1 
> -----Original Message-----
> From: liulongfang <liulongfang@huawei.com>
> Sent: Tuesday, March 4, 2025 12:05 PM
> To: alex.williamson@redhat.com; jgg@nvidia.com; Shameerali Kolothum
> Thodi <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>
> Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org;
> linuxarm@openeuler.org; liulongfang <liulongfang@huawei.com>
> Subject: [PATCH v2 0/3] update live migration configuration region
> 
> On the new hardware platform, the configuration register space
> of the live migration function is set on the PF, while on the
> old platform, this part is placed on the VF.
> 
> Change v1 -> v2
> 	Delete the vf_qm_state read operation in Pre_Copy

If I understand correctly, previously this was discussed in your bug fix series here,
https://lore.kernel.org/all/fa8cd8c1cdbe4849b445ffd8f4894515@huawei.com/

And why we are having it here in this new hardware support series now?

Could we please move all the existing bug fixes in one series and support for
new platform in another series, please.

Thanks,
Shameer
Longfang Liu March 4, 2025, 12:33 p.m. UTC | #2 
On 2025/3/4 20:26, Shameerali Kolothum Thodi wrote:
> 
> 
>> -----Original Message-----
>> From: liulongfang <liulongfang@huawei.com>
>> Sent: Tuesday, March 4, 2025 12:05 PM
>> To: alex.williamson@redhat.com; jgg@nvidia.com; Shameerali Kolothum
>> Thodi <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
>> <jonathan.cameron@huawei.com>
>> Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org;
>> linuxarm@openeuler.org; liulongfang <liulongfang@huawei.com>
>> Subject: [PATCH v2 0/3] update live migration configuration region
>>
>> On the new hardware platform, the configuration register space
>> of the live migration function is set on the PF, while on the
>> old platform, this part is placed on the VF.
>>
>> Change v1 -> v2
>> 	Delete the vf_qm_state read operation in Pre_Copy
> 
> If I understand correctly, previously this was discussed in your bug fix series here,
> https://lore.kernel.org/all/fa8cd8c1cdbe4849b445ffd8f4894515@huawei.com/
> 
> And why we are having it here in this new hardware support series now?
> 
> Could we please move all the existing bug fixes in one series and support for
> new platform in another series, please.
> 
> Thanks,
> Shameer
> 
> .
> 

OK, I'll separate it out and put it in the bugfix patchset

Thanks.
Longfang.