From: Alex Williamson <alex.williamson@redhat.com>
To: Longfang Liu <liulongfang@huawei.com>
Cc: <jgg@nvidia.com>, <shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH v14 0/4] debugfs to hisilicon migration driver
Date: Fri, 8 Nov 2024 14:01:21 -0700 [thread overview]
Message-ID: <20241108140121.1032a68a.alex.williamson@redhat.com> (raw)
In-Reply-To: <20241108065538.45710-1-liulongfang@huawei.com>
On Fri, 8 Nov 2024 14:55:34 +0800
Longfang Liu <liulongfang@huawei.com> wrote:
> Add a debugfs function to the hisilicon migration driver in VFIO to
> provide intermediate state values and data during device migration.
>
> When the execution of live migration fails, the user can view the
> status and data during the migration process separately from the
> source and the destination, which is convenient for users to analyze
> and locate problems.
>
> Changes v13 -> v14
> Bugfix the parameter problem of seq_puts()
Should we assume this one is at least compile tested? Thanks,
Alex
>
> Changes v12 -> v13
> Replace seq_printf() with seq_puts()
>
> Changes v11 -> v12
> Update comments and delete unnecessary logs
>
> Changes v10 -> v11
> Update conditions for debugfs registration
>
> Changes v9 -> v10
> Optimize symmetry processing of mutex
>
> Changes v8 -> v9
> Added device enable mutex
>
> Changes v7 -> v8
> Delete unnecessary information
>
> Changes v6 -> v7
> Remove redundant kernel error log printing and
> remove unrelated bugfix code
>
> Changes v5 -> v6
> Modify log output calling error
>
> Changes v4 -> v5
> Adjust the descriptioniptionbugfs file directory
>
> Changes v3 -> v4
> Rebased on kernel6.9
>
> Changes 2 -> v3
> Solve debugfs serialization problem.
>
> Changes v1 -> v2
> Solve the racy problem of io_base.
>
> Longfang Liu (4):
> hisi_acc_vfio_pci: extract public functions for container_of
> hisi_acc_vfio_pci: create subfunction for data reading
> hisi_acc_vfio_pci: register debugfs for hisilicon migration driver
> Documentation: add debugfs description for hisi migration
>
> .../ABI/testing/debugfs-hisi-migration | 25 ++
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 266 ++++++++++++++++--
> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 19 ++
> 3 files changed, 279 insertions(+), 31 deletions(-)
> create mode 100644 Documentation/ABI/testing/debugfs-hisi-migration
>
next prev parent reply other threads:[~2024-11-08 21:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 6:55 Longfang Liu
2024-11-08 6:55 ` [PATCH v14 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-11-08 6:55 ` [PATCH v14 2/4] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-11-08 6:55 ` [PATCH v14 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-11-08 6:55 ` [PATCH v14 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-11-08 21:01 ` Alex Williamson [this message]
2024-11-11 13:59 ` [PATCH v14 0/4] debugfs to hisilicon migration driver liulongfang
2024-11-12 8:15 ` 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=20241108140121.1032a68a.alex.williamson@redhat.com \
--to=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=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®