public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: liulongfang <liulongfang@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: <jgg@nvidia.com>, <shameerali.kolothum.thodi@huawei.com>,
	<jonathan.cameron@huawei.com>, <bcreeley@amd.com>,
	<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linuxarm@openeuler.org>
Subject: Re: [PATCH v19 0/3] add debugfs to migration driver
Date: Mon, 11 Dec 2023 09:21:27 +0800	[thread overview]
Message-ID: <4744fd4d-e8de-e079-0acf-acc363d5caaf@huawei.com> (raw)
In-Reply-To: <20231204170040.7703f1e1.alex.williamson@redhat.com>

On 2023/12/5 8:00, Alex Williamson wrote:
> On Mon, 6 Nov 2023 15:22:22 +0800
> Longfang Liu <liulongfang@huawei.com> wrote:
> 
>> Add a debugfs function to the migration driver in VFIO to provide
>> a step-by-step debugfs information for the migration driver.
>>
>> Changes v18 -> v19
>> 	maintainers add a patch.
>>
>> Changes v17 -> v18
>> 	Replace seq_printf() with seq_puts().
>>
>> Changes v16 -> v17
>> 	Add separate VFIO_DEBUGFS Kconfig entries.
>>
>> Changes v15 -> v16
>> 	Update the calling order of functions to maintain symmetry
>>
>> Changes v14 -> v15
>> 	Update the output status value of live migration.
>>
>> Changes v13 -> v14
>> 	Split the patchset and keep the vfio debugfs frame.
>>
>> Changes v12 -> v13
>> 	Solve the problem of open and close competition to debugfs.
>>
>> Changes v11 -> v12
>> 	Update loading conditions of vfio debugfs.
>>
>> 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 (3):
>>   vfio/migration: Add debugfs to live migration driver
>>   Documentation: add debugfs description for vfio
>>   MAINTAINERS: Update the maintenance directory of vfio driver
>>
>>  Documentation/ABI/testing/debugfs-vfio | 25 +++++++
>>  MAINTAINERS                            |  1 +
>>  drivers/vfio/Kconfig                   | 10 +++
>>  drivers/vfio/Makefile                  |  1 +
>>  drivers/vfio/debugfs.c                 | 90 ++++++++++++++++++++++++++
>>  drivers/vfio/vfio.h                    | 14 ++++
>>  drivers/vfio/vfio_main.c               |  4 ++
>>  include/linux/vfio.h                   |  7 ++
>>  include/uapi/linux/vfio.h              |  1 +
>>  9 files changed, 153 insertions(+)
>>  create mode 100644 Documentation/ABI/testing/debugfs-vfio
>>  create mode 100644 drivers/vfio/debugfs.c
>>
> 
> Applied to vfio next branch for v6.8.  I resolved some whitespace
> issues and updated the date and kernel release version in the
> Documentation as well.  Thanks,
> 

OK, thank you very much!

Longfang.

> Alex
> 
> .
> 

      reply	other threads:[~2023-12-11  1:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06  7:22 [PATCH v19 0/3] add debugfs to migration driver Longfang Liu
2023-11-06  7:22 ` [PATCH v19 1/3] vfio/migration: Add debugfs to live " Longfang Liu
2023-11-06  7:22 ` [PATCH v19 2/3] Documentation: add debugfs description for vfio Longfang Liu
2023-11-06  7:22 ` [PATCH v19 3/3] MAINTAINERS: Update the maintenance directory of vfio driver Longfang Liu
2023-12-01  3:08 ` [PATCH v19 0/3] add debugfs to migration driver liulongfang
2023-12-05  0:00 ` Alex Williamson
2023-12-11  1:21   ` 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=4744fd4d-e8de-e079-0acf-acc363d5caaf@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=bcreeley@amd.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