From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: liulongfang <liulongfang@huawei.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"jgg@nvidia.com" <jgg@nvidia.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: RE: [PATCH v7 4/4] Documentation: add debugfs description for hisi migration
Date: Mon, 5 Aug 2024 09:09:37 +0000 [thread overview]
Message-ID: <6b13310df6df42faba08eb7335c4b33b@huawei.com> (raw)
In-Reply-To: <20240730121438.58455-5-liulongfang@huawei.com>
> -----Original Message-----
> From: liulongfang <liulongfang@huawei.com>
> Sent: Tuesday, July 30, 2024 1:15 PM
> To: alex.williamson@redhat.com; jgg@nvidia.com; Shameerali Kolothum
> Thodi <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>
> Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org;
> linuxarm@openeuler.org; liulongfang <liulongfang@huawei.com>
> Subject: [PATCH v7 4/4] Documentation: add debugfs description for hisi
> migration
>
> 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 | 25 +++++++++++++++++++
> 1 file changed, 25 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..053f3ebba9b1
> --- /dev/null
> +++ b/Documentation/ABI/testing/debugfs-hisi-migration
> @@ -0,0 +1,25 @@
> +What:
> /sys/kernel/debug/vfio/<device>/migration/hisi_acc/dev_data
> +Date: Jul 2024
> +KernelVersion: 6.11
> +Contact: Longfang Liu <liulongfang@huawei.com>
> +Description: Read the configuration data and some status data
> + required for device live migration. These data include device
> + status data, queue configuration data, some task
> configuration
> + data and device attribute data. The output format of the data
> + is defined by the live migration driver.
> +
> +What:
> /sys/kernel/debug/vfio/<device>/migration/hisi_acc/migf_data
> +Date: Jul 2024
> +KernelVersion: 6.11
> +Contact: Longfang Liu <liulongfang@huawei.com>
> +Description: Read the data from the last completed live migration.
> + This data includes the same device status data as in
> "dev_data".
> + And some device status data after the migration is
> completed.
Actually what info is different from dev_data here? Only that it is the
dev_data after a migration is attempted/completed, right?
Thanks,
Shameer
> +
> +What:
> /sys/kernel/debug/vfio/<device>/migration/hisi_acc/cmd_state
> +Date: Jul 2024
> +KernelVersion: 6.11
> +Contact: Longfang Liu <liulongfang@huawei.com>
> +Description: Used to obtain the device command sending and receiving
> + channel status. Returns failure or success logs based on the
> + results.
> --
> 2.24.0
next prev parent reply other threads:[~2024-08-05 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 12:14 [PATCH v7 0/4] debugfs to hisilicon migration driver Longfang Liu
2024-07-30 12:14 ` [PATCH v7 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-08-05 9:11 ` Shameerali Kolothum Thodi
2024-07-30 12:14 ` [PATCH v7 2/4] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-08-05 9:12 ` Shameerali Kolothum Thodi
2024-07-30 12:14 ` [PATCH v7 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-08-05 8:51 ` Shameerali Kolothum Thodi
2024-08-06 8:30 ` liulongfang
2024-07-30 12:14 ` [PATCH v7 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-08-05 9:09 ` Shameerali Kolothum Thodi [this message]
2024-08-06 8:37 ` 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=6b13310df6df42faba08eb7335c4b33b@huawei.com \
--to=shameerali.kolothum.thodi@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=liulongfang@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