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 v10 0/4] debugfs to hisilicon migration driver
Date: Thu, 24 Oct 2024 13:18:55 +0000 [thread overview]
Message-ID: <3ede2cf97ffd4dd6948aa06084a09d2d@huawei.com> (raw)
In-Reply-To: <20241016012308.14108-1-liulongfang@huawei.com>
Hi Alex,
> -----Original Message-----
> From: liulongfang <liulongfang@huawei.com>
> Sent: Wednesday, October 16, 2024 2:23 AM
> 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 v10 0/4] debugfs to hisilicon migration driver
>
> Add a debugfs function to the hisilicon migration driver in VFIO to
> provide intermediate state values and data during device migration.
>
> 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.
Could you please take another look at this series as it looks like almost there.
Thanks,
Shameer
next prev parent reply other threads:[~2024-10-24 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 1:23 [PATCH v10 0/4] debugfs to hisilicon migration driver Longfang Liu
2024-10-16 1:23 ` [PATCH v10 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-10-16 1:23 ` [PATCH v10 2/4] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-10-16 1:23 ` [PATCH v10 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-10-24 13:12 ` Shameerali Kolothum Thodi
2024-10-24 13:26 ` liulongfang
2024-10-16 1:23 ` [PATCH v10 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-10-24 13:14 ` Shameerali Kolothum Thodi
2024-10-24 13:18 ` Shameerali Kolothum Thodi [this message]
2024-10-24 15:27 ` [PATCH v10 0/4] debugfs to hisilicon migration driver Jason Gunthorpe
2024-10-24 16:06 ` Shameerali Kolothum Thodi
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=3ede2cf97ffd4dd6948aa06084a09d2d@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