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 v16 2/2] Documentation: add debugfs description for vfio
Date: Fri, 13 Oct 2023 16:16:25 +0800 [thread overview]
Message-ID: <dbd0de80-1646-87b7-5d97-48a5bd7a174b@huawei.com> (raw)
In-Reply-To: <20231003132635.7df44c44.alex.williamson@redhat.com>
On 2023/10/4 3:26, Alex Williamson wrote:
> On Tue, 26 Sep 2023 17:33:56 +0800
> liulongfang <liulongfang@huawei.com> wrote:
>
>> From: Longfang Liu <liulongfang@huawei.com>
>>
>> 1.Add an debugfs document description file to help users understand
>> how to use the accelerator live migration driver's debugfs.
>> 2.Update the file paths that need to be maintained in MAINTAINERS
>>
>> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
>> ---
>> Documentation/ABI/testing/debugfs-vfio | 25 +++++++++++++++++++++++++
>> MAINTAINERS | 1 +
>> 2 files changed, 26 insertions(+)
>> create mode 100644 Documentation/ABI/testing/debugfs-vfio
>>
>> diff --git a/Documentation/ABI/testing/debugfs-vfio b/Documentation/ABI/testing/debugfs-vfio
>> new file mode 100644
>> index 000000000000..7959ec5ac445
>> --- /dev/null
>> +++ b/Documentation/ABI/testing/debugfs-vfio
>> @@ -0,0 +1,25 @@
>> +What: /sys/kernel/debug/vfio
>> +Date: Sep 2023
>> +KernelVersion: 6.7
>> +Contact: Longfang Liu <liulongfang@huawei.com>
>> +Description: This debugfs file directory is used for debugging
>> + of vfio devices, it's a common directory for all vfio devices.
>> + Vfio core will create a device subdirectory under this
>> + directory.
>> +
>> +What: /sys/kernel/debug/vfio/<device>/migration
>> +Date: Sep 2023
>> +KernelVersion: 6.7
>> +Contact: Longfang Liu <liulongfang@huawei.com>
>> +Description: This debugfs file directory is used for debugging
>> + of vfio devices that support live migration.
>> + The debugfs of each vfio device that supports live migration
>> + could be created under this directory.
>> +
>> +What: /sys/kernel/debug/vfio/<device>/migration/state
>> +Date: Sep 2023
>> +KernelVersion: 6.7
>> +Contact: Longfang Liu <liulongfang@huawei.com>
>> +Description: Read the live migration status of the vfio device.
>> + The status of these live migrations includes:
>> + ERROR, RUNNING, STOP, STOP_COPY, RESUMING.
>
> This is another area that's doomed to be out of sync, it's already not
> updated for P2P states. Better to avoid the problem and say something
> like "The contents of the state file reflects the migration state
> relative to those defined in the vfio_device_mig_state enum".
>
> Also, as suggested last time, October is a more realistic date. Thanks,
>
OK, I will modify it in the next version
Thanks
Longfang.
> Alex
>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 7b1306615fc0..bd01ca674c60 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -22304,6 +22304,7 @@ L: kvm@vger.kernel.org
>> S: Maintained
>> T: git https://github.com/awilliam/linux-vfio.git
>> F: Documentation/ABI/testing/sysfs-devices-vfio-dev
>> +F: Documentation/ABI/testing/debugfs-vfio
>> F: Documentation/driver-api/vfio.rst
>> F: drivers/vfio/
>> F: include/linux/vfio.h
>
> .
>
prev parent reply other threads:[~2023-10-13 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 9:33 [PATCH v16 0/2] add debugfs to migration driver liulongfang
2023-09-26 9:33 ` [PATCH v16 1/2] vfio/migration: Add debugfs to live " liulongfang
2023-10-03 19:26 ` Alex Williamson
2023-10-13 8:09 ` liulongfang
2023-09-26 9:33 ` [PATCH v16 2/2] Documentation: add debugfs description for vfio liulongfang
2023-10-03 19:26 ` Alex Williamson
2023-10-13 8:16 ` 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=dbd0de80-1646-87b7-5d97-48a5bd7a174b@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
all inboxes | Powered by JetHome®