mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v4 4/4] Documentation: add debugfs description for hisi migration
Date: Thu, 4 Apr 2024 14:07:50 -0600	[thread overview]
Message-ID: <20240404140750.78549701.alex.williamson@redhat.com> (raw)
In-Reply-To: <20240402032432.41004-5-liulongfang@huawei.com>

On Tue, 2 Apr 2024 11:24:32 +0800
Longfang Liu <liulongfang@huawei.com> wrote:

> Add a debugfs document description file to help users understand
> how to use the hisilicon accelerator live migration driver's
> debugfs.
> 
> Update the file paths that need to be maintained in MAINTAINERS
> 
> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> ---
>  .../ABI/testing/debugfs-hisi-migration        | 34 +++++++++++++++++++
>  MAINTAINERS                                   |  1 +
>  2 files changed, 35 insertions(+)
>  create mode 100644 Documentation/ABI/testing/debugfs-hisi-migration
> 
> diff --git a/Documentation/ABI/testing/debugfs-hisi-migration b/Documentation/ABI/testing/debugfs-hisi-migration
> new file mode 100644
> index 000000000000..3d7339276e6f
> --- /dev/null
> +++ b/Documentation/ABI/testing/debugfs-hisi-migration
> @@ -0,0 +1,34 @@
> +What:		/sys/kernel/debug/vfio/<device>/migration/hisi_acc/data
> +Date:		Apr 2024
> +KernelVersion:  6.9

At best 6.10 with a merge window in May.

> +Contact:	Longfang Liu <liulongfang@huawei.com>
> +Description:	Read the live migration data of the vfio device.
> +		These data include device status data, queue configuration
> +		data and some task configuration data.
> +		The output format of the data is defined by the live
> +		migration driver.

"Dumps the device debug migration buffer, state must first be saved
using the 'save' attribute."

> +
> +What:		/sys/kernel/debug/vfio/<device>/migration/hisi_acc/attr
> +Date:		Apr 2024
> +KernelVersion:  6.9
> +Contact:	Longfang Liu <liulongfang@huawei.com>
> +Description:	Read the live migration attributes of the vfio device.
> +		it include device status attributes and data length attributes
> +		The output format of the attributes is defined by the live
> +		migration driver.

AFAICT from the previous patch, this attribute is useless.

> +
> +What:		/sys/kernel/debug/vfio/<device>/migration/hisi_acc/cmd_state
> +Date:		Apr 2024
> +KernelVersion:  6.9
> +Contact:	Longfang Liu <liulongfang@huawei.com>
> +Description:	Used to obtain the device command sending and receiving
> +		channel status. If successful, returns the command value.
> +		If failed, return error log.
> +

Seems like it statically returns "OK" plus the actual value.


> +What:		/sys/kernel/debug/vfio/<device>/migration/hisi_acc/save
> +Date:		Apr 2024
> +KernelVersion:  6.9
> +Contact:	Longfang Liu <liulongfang@huawei.com>
> +Description:	Trigger the Hisilicon accelerator device to perform
> +		the state saving operation of live migration through the read
> +		operation, and output the operation log results.

These interfaces are confusing, attr and data only work if there has
either been a previous save OR the user migration process closed saving
or resuming fds in the interim, and the user doesn't know which one
they get.  Note that debug_migf isn't even discarded between
open/close, only cmd and save require the device to be opened by a
user, data and attr might continue to return data from some previous
user save, resume, or debugfs save.



> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7625911ec2f1..8c2d13b13273 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -23072,6 +23072,7 @@ M:	Longfang Liu <liulongfang@huawei.com>
>  M:	Shameer Kolothum <shameerali.kolothum.thodi@huawei.com>
>  L:	kvm@vger.kernel.org
>  S:	Maintained
> +F:	Documentation/ABI/testing/debugfs-hisi-migration
>  F:	drivers/vfio/pci/hisilicon/
>  
>  VFIO MEDIATED DEVICE DRIVERS


  reply	other threads:[~2024-04-04 20:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  3:24 [PATCH v4 0/4] add debugfs to hisilicon migration driver Longfang Liu
2024-04-02  3:24 ` [PATCH v4 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-04-02  3:24 ` [PATCH v4 2/4] hisi_acc_vfio_pci: Create subfunction for data reading Longfang Liu
2024-04-04 20:07   ` Alex Williamson
2024-04-12  3:07     ` liulongfang
2024-04-02  3:24 ` [PATCH v4 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-04-04 20:07   ` Alex Williamson
2024-04-12  8:15     ` liulongfang
2024-04-24  3:15       ` liulongfang
2024-04-02  3:24 ` [PATCH v4 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-04-04 20:07   ` Alex Williamson [this message]
2024-04-12  3:02     ` 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=20240404140750.78549701.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®