From: Alex Williamson <alex@shazbot.org>
To: Longfang Liu <liulongfang@huawei.com>
Cc: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<herbert@gondor.apana.org.au>, <shameerkolothum@gmail.com>,
<jonathan.cameron@huawei.com>, <linux-crypto@vger.kernel.org>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v12 0/2] update live migration configuration region
Date: Thu, 6 Nov 2025 21:34:47 -0700 [thread overview]
Message-ID: <20251106213447.76dc2e3f.alex@shazbot.org> (raw)
In-Reply-To: <20251030015744.131771-1-liulongfang@huawei.com>
On Thu, 30 Oct 2025 09:57:42 +0800
Longfang Liu <liulongfang@huawei.com> 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 v11 -> v12
> Standardize register BIT operations
...
>
> 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(-)
Applied to vfio next branch for v6.19 with discussed enum field change.
Thanks,
Alex
prev parent reply other threads:[~2025-11-07 4:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 1:57 [PATCH v12 0/2] update live migration configuration region Longfang Liu
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 ` Alex Williamson [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=20251106213447.76dc2e3f.alex@shazbot.org \
--to=alex@shazbot.org \
--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=liulongfang@huawei.com \
--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