From: Herbert Xu <herbert@gondor.apana.org.au>
To: liulongfang <liulongfang@huawei.com>
Cc: alex.williamson@redhat.com, jgg@nvidia.com,
shameerali.kolothum.thodi@huawei.com,
jonathan.cameron@huawei.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxarm@openeuler.org,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v5 2/3] migration: qm updates BAR configuration
Date: Sun, 27 Jul 2025 20:45:11 +0800 [thread overview]
Message-ID: <aIYfVyBp6trHWnwj@gondor.apana.org.au> (raw)
In-Reply-To: <7694ee87-2852-3759-1360-6349f46e7d70@huawei.com>
On Tue, Jul 15, 2025 at 03:23:09PM +0800, liulongfang wrote:
> On 2025/6/30 16:54, Longfang Liu wrote:
> > On new platforms greater than QM_HW_V3, the configuration region for the
> > live migration function of the accelerator device is no longer
> > placed in the VF, but is instead placed in the PF.
> >
> > Therefore, the configuration region of the live migration function
> > needs to be opened when the QM driver is loaded. When the QM driver
> > is uninstalled, the driver needs to clear this configuration.
> >
> > Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> > ---
> > drivers/crypto/hisilicon/qm.c | 29 +++++++++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
>
> Hello, Herbert. There is a patch in this patchset that modifies the crypto subsystem.
> Could you help review it?
Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2025-07-27 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 8:53 [PATCH v5 0/3] update live migration configuration region Longfang Liu
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 [this message]
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=aIYfVyBp6trHWnwj@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=alex.williamson@redhat.com \
--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=liulongfang@huawei.com \
--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®