From: liulongfang <liulongfang@huawei.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: [PATCH v2 0/3] update live migration configuration region
Date: Tue, 4 Mar 2025 20:33:55 +0800 [thread overview]
Message-ID: <bcc0f7bd-8e84-3f10-9985-91741c688fd8@huawei.com> (raw)
In-Reply-To: <0b5399e306f841b794120e6ca91c1edd@huawei.com>
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.
prev parent reply other threads:[~2025-03-04 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 12:05 Longfang Liu
2025-03-04 12:05 ` [PATCH v2 1/3] migration: update BAR space size Longfang Liu
2025-03-04 12:05 ` [PATCH v2 2/3] migration: qm updates BAR configuration Longfang Liu
2025-03-04 12:05 ` [PATCH v2 3/3] migration: adapt to new migration configuration Longfang Liu
2025-03-04 12:26 ` [PATCH v2 0/3] update live migration configuration region Shameerali Kolothum Thodi
2025-03-04 12:33 ` liulongfang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bcc0f7bd-8e84-3f10-9985-91741c688fd8@huawei.com \
--to=liulongfang@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.org \
--cc=shameerali.kolothum.thodi@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®