The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: liulongfang <liulongfang@huawei.com>
To: <alex.williamson@redhat.com>, <jgg@nvidia.com>,
	<shameerali.kolothum.thodi@huawei.com>,
	<jonathan.cameron@huawei.com>
Cc: <cohuck@redhat.com>, <linux-kernel@vger.kernel.org>,
	<linuxarm@openeuler.org>
Subject: Re: [PATCH v11 0/4] add debugfs to migration driver
Date: Mon, 10 Jul 2023 20:12:46 +0800	[thread overview]
Message-ID: <9c3f7b5c-b0c0-2c74-e32f-68fd3e1deee9@huawei.com> (raw)
In-Reply-To: <20230630092457.54902-1-liulongfang@huawei.com>

On 2023/6/30 17:24, liulongfang wrote:
> Add a debugfs function to the migration driver in VFIO to provide
> a step-by-step test function for the migration driver.
> 
> 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 v10 -> v11
> 	Delete the device restore function in debugfs.
> 
> Changes v9 -> v10
> 	Update the debugfs file of the live migration driver.
> 
> Changes v8 -> v9
> 	Update the debugfs directory structure of vfio.
> 
> Changes v7 -> v8
> 	Add support for platform devices.
> 
> Changes v6 -> v7
> 	Fix some code style issues.
> 
> Changes v5 -> v6
> 	Control the creation of debugfs through the CONFIG_DEBUG_FS.
> 
> Changes v4 -> v5
> 	Remove the newly added vfio_migration_ops and use seq_printf
> 	to optimize the implementation of debugfs.
> 
> Changes v3 -> v4
> 	Change the migration_debug_operate interface to debug_root file.
> 
> Changes v2 -> v3
> 	Extend the debugfs function from hisilicon device to vfio.
> 
> Changes v1 -> v2
> 	Change the registration method of root_debugfs to register
> 	with module initialization. 
> 
> Longfang Liu (4):
>   vfio/migration: Add debugfs to live migration driver
>   hisi_acc_vfio_pci: extract public functions for container_of
>   hisi_acc_vfio_pci: register debugfs for hisilicon migration driver
>   Documentation: add debugfs description for vfio
> 
>  .../ABI/testing/debugfs-hisi-migration        |  32 +++
>  Documentation/ABI/testing/debugfs-vfio        |  25 +++
>  MAINTAINERS                                   |   2 +
>  drivers/vfio/Makefile                         |   1 +
>  .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    | 203 +++++++++++++++++-
>  .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h    |  11 +
>  drivers/vfio/vfio.h                           |  14 ++
>  drivers/vfio/vfio_debugfs.c                   |  78 +++++++
>  drivers/vfio/vfio_main.c                      |   9 +-
>  include/linux/vfio.h                          |   7 +
>  10 files changed, 371 insertions(+), 11 deletions(-)
>  create mode 100644 Documentation/ABI/testing/debugfs-hisi-migration
>  create mode 100644 Documentation/ABI/testing/debugfs-vfio
>  create mode 100644 drivers/vfio/vfio_debugfs.c
> 

Hi, Alex
Can you help me to review these patches ?

Thanks,
Longfang.

      parent reply	other threads:[~2023-07-10 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30  9:24 [PATCH v11 0/4] add debugfs to migration driver liulongfang
2023-06-30  9:24 ` [PATCH v11 1/4] vfio/migration: Add debugfs to live " liulongfang
2023-07-18 17:45   ` Cédric Le Goater
2023-07-24  2:42     ` liulongfang
2023-06-30  9:24 ` [PATCH v11 2/4] hisi_acc_vfio_pci: extract public functions for container_of liulongfang
2023-06-30  9:24 ` [PATCH v11 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver liulongfang
2023-07-14 22:07   ` Alex Williamson
2023-07-24  3:14     ` liulongfang
2023-06-30  9:24 ` [PATCH v11 4/4] Documentation: add debugfs description for vfio liulongfang
2023-07-14 22:07   ` Alex Williamson
2023-07-24  4:00     ` liulongfang
2023-07-10 12:12 ` 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=9c3f7b5c-b0c0-2c74-e32f-68fd3e1deee9@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=jonathan.cameron@huawei.com \
    --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