From: liulongfang <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<herbert@gondor.apana.org.au>,
<shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>
Cc: <linux-crypto@vger.kernel.org>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH v7 0/3] update live migration configuration region
Date: Tue, 19 Aug 2025 17:14:41 +0800 [thread overview]
Message-ID: <b9c290a4-c1ba-6e5f-631c-c80dbda76d56@huawei.com> (raw)
In-Reply-To: <20250805065106.898298-1-liulongfang@huawei.com>
On 2025/8/5 14:51, Longfang Liu wrote:
> 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 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 (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 | 200 ++++++++++++------
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 7 +
> 3 files changed, 174 insertions(+), 62 deletions(-)
>
Hello, Alex.
Could this patchset be merged into the next branch?
Thanks.
Longfang.
prev parent reply other threads:[~2025-08-19 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:51 Longfang Liu
2025-08-05 6:51 ` [PATCH v7 1/3] migration: update BAR space size Longfang Liu
2025-08-05 6:51 ` [PATCH v7 2/3] migration: qm updates BAR configuration Longfang Liu
2025-08-19 9:12 ` liulongfang
2025-08-19 9:53 ` Herbert Xu
2025-08-19 10:56 ` liulongfang
2025-08-05 6:51 ` [PATCH v7 3/3] migration: adapt to new migration configuration Longfang Liu
2025-08-19 21:35 ` Alex Williamson
2025-08-20 1:53 ` liulongfang
2025-08-19 9:14 ` 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=b9c290a4-c1ba-6e5f-631c-c80dbda76d56@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=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®