linux-kernel - RE: [PATCH v2 0/3] update live migration configuration region

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 for Android: free password hash cracker in your pocket

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

Message-ID: <0b5399e306f841b794120e6ca91c1edd@huawei.com>
Date: Tue, 4 Mar 2025 12:26:59 +0000
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@...wei.com>
To: liulongfang <liulongfang@...wei.com>, "alex.williamson@...hat.com"
	<alex.williamson@...hat.com>, "jgg@...dia.com" <jgg@...dia.com>, "Jonathan
 Cameron" <jonathan.cameron@...wei.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linuxarm@...neuler.org" <linuxarm@...neuler.org>
Subject: RE: [PATCH v2 0/3] update live migration configuration region



> -----Original Message-----
> From: liulongfang <liulongfang@...wei.com>
> Sent: Tuesday, March 4, 2025 12:05 PM
> To: alex.williamson@...hat.com; jgg@...dia.com; Shameerali Kolothum
> Thodi <shameerali.kolothum.thodi@...wei.com>; Jonathan Cameron
> <jonathan.cameron@...wei.com>
> Cc: kvm@...r.kernel.org; linux-kernel@...r.kernel.org;
> linuxarm@...neuler.org; liulongfang <liulongfang@...wei.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