From: Longfang Liu <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<herbert@gondor.apana.org.au>, <shameerkolothum@gmail.com>,
<jonathan.cameron@huawei.com>
Cc: <linux-crypto@vger.kernel.org>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <liulongfang@huawei.com>
Subject: [PATCH v12 0/2] update live migration configuration region
Date: Thu, 30 Oct 2025 09:57:42 +0800 [thread overview]
Message-ID: <20251030015744.131771-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 v11 -> v12
Standardize register BIT operations
Change v10 -> v11
Remove redundant register read/write helper functions
Change v9 -> v10
Update the name of the configuration mode
Change v8 -> v9
Update the version name for driver matching
Change v7 -> v8
Resolve hardware compatibility issues.
Change v6 -> v7
Update the comment of the live migration configuration scheme.
Change v5 -> v6
Update VF device properties
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 (2):
crypto: hisilicon - qm updates BAR configuration
hisi_acc_vfio_pci: adapt to new migration configuration
drivers/crypto/hisilicon/qm.c | 27 ++++
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 130 +++++++++++++-----
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 23 +++-
include/linux/hisi_acc_qm.h | 3 +
4 files changed, 144 insertions(+), 39 deletions(-)
--
2.33.0
next reply other threads:[~2025-10-30 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 1:57 Longfang Liu [this message]
2025-10-30 1:57 ` [PATCH v12 1/2] crypto: hisilicon - qm updates BAR configuration Longfang Liu
2025-10-30 1:57 ` [PATCH v12 2/2] hisi_acc_vfio_pci: adapt to new migration configuration Longfang Liu
2025-11-05 22:32 ` Alex Williamson
2025-11-06 2:26 ` liulongfang
2025-11-07 4:34 ` [PATCH v12 0/2] update live migration configuration region Alex Williamson
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=20251030015744.131771-1-liulongfang@huawei.com \
--to=liulongfang@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shameerkolothum@gmail.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