From: Longfang Liu <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
<shameerali.kolothum.thodi@huawei.com>,
<jonathan.cameron@huawei.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linuxarm@openeuler.org>, <liulongfang@huawei.com>
Subject: [PATCH v3 0/4] add debugfs to hisilicon migration driver
Date: Thu, 7 Mar 2024 14:03:49 +0800 [thread overview]
Message-ID: <20240307060353.16095-1-liulongfang@huawei.com> (raw)
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 v2 -> 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 | 34 +++
MAINTAINERS | 1 +
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 280 +++++++++++++++---
.../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 14 +
4 files changed, 294 insertions(+), 35 deletions(-)
create mode 100644 Documentation/ABI/testing/debugfs-hisi-migration
--
2.24.0
next reply other threads:[~2024-03-07 6:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 6:03 Longfang Liu [this message]
2024-03-07 6:03 ` [PATCH v3 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-03-07 6:03 ` [PATCH v3 2/4] hisi_acc_vfio_pci: Create subfunction for data reading Longfang Liu
2024-03-07 8:33 ` Shameerali Kolothum Thodi
2024-03-07 11:51 ` 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=20240307060353.16095-1-liulongfang@huawei.com \
--to=liulongfang@huawei.com \
--cc=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=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®