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>, <kvm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [PATCH v15 0/4] debugfs to hisilicon migration driver
Date: Fri, 15 Nov 2024 16:36:34 +0800 [thread overview]
Message-ID: <8a193de7-fffe-a2c8-2964-aa4fe3771f1c@huawei.com> (raw)
In-Reply-To: <20241114121225.3ab59ce6.alex.williamson@redhat.com>
On 2024/11/15 3:12, Alex Williamson wrote:
> On Tue, 12 Nov 2024 15:33:18 +0800
> Longfang Liu <liulongfang@huawei.com> wrote:
>
>> 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.
>>
>> Changes v14 -> v15
>> Correct variable declaration type
>
> Applied to vfio next branch for v6.13. Thanks,
>
> Alex
>
Thanks.
Longfang
>
> .
>
prev parent reply other threads:[~2024-11-15 8:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 7:33 [PATCH v15 0/4] debugfs to hisilicon migration driver Longfang Liu
2024-11-12 7:33 ` [PATCH v15 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-11-12 7:33 ` [PATCH v15 2/4] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-11-12 7:33 ` [PATCH v15 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-11-12 8:40 ` Shameerali Kolothum Thodi
2024-11-12 21:50 ` Alex Williamson
2024-11-13 7:59 ` Shameerali Kolothum Thodi
2024-11-12 7:33 ` [PATCH v15 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-11-14 19:12 ` [PATCH v15 0/4] debugfs to hisilicon migration driver Alex Williamson
2024-11-15 8:36 ` 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=8a193de7-fffe-a2c8-2964-aa4fe3771f1c@huawei.com \
--to=liulongfang@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=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