From: Longfang Liu <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@openeuler.org>, <liulongfang@huawei.com>
Subject: [PATCH v5 0/3] update live migration configuration region
Date: Mon, 30 Jun 2025 16:53:59 +0800 [thread overview]
Message-ID: <20250630085402.7491-1-liulongfang@huawei.com> (raw)
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 v4 -> v5
Remove BAR length alignment
Change v3 -> v4
Rebase on kernel 6.15
Change v2 -> v3
Put the changes of Pre_Copy into another bugfix patchset.
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 | 29 +++
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 202 ++++++++++++------
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 7 +
3 files changed, 176 insertions(+), 62 deletions(-)
--
2.24.0
next reply other threads:[~2025-06-30 8:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 8:53 Longfang Liu [this message]
2025-06-30 8:54 ` [PATCH v5 1/3] migration: update BAR space size Longfang Liu
2025-07-08 8:02 ` Shameerali Kolothum Thodi
2025-07-15 7:25 ` liulongfang
2025-06-30 8:54 ` [PATCH v5 2/3] migration: qm updates BAR configuration Longfang Liu
2025-07-08 8:18 ` Shameerali Kolothum Thodi
2025-07-15 7:16 ` liulongfang
2025-07-15 7:23 ` liulongfang
2025-07-27 12:45 ` Herbert Xu
2025-06-30 8:54 ` [PATCH v5 3/3] migration: adapt to new migration configuration Longfang Liu
2025-07-08 8:28 ` Shameerali Kolothum Thodi
2025-07-15 7:15 ` liulongfang
2025-07-15 7:49 ` liulongfang
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=20250630085402.7491-1-liulongfang@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®