public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: liulongfang <liulongfang@huawei.com>,
	"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	"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 16:06:22 +0000	[thread overview]
Message-ID: <5d0a9221a3b84ea88d2f77197f913091@huawei.com> (raw)
In-Reply-To: <20241024152749.GB6956@nvidia.com>



> -----Original Message-----
> From: Jason Gunthorpe <jgg@nvidia.com>
> Sent: Thursday, October 24, 2024 4:28 PM
> To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
> Cc: liulongfang <liulongfang@huawei.com>; alex.williamson@redhat.com;
> Jonathan Cameron <jonathan.cameron@huawei.com>;
> kvm@vger.kernel.org; linux-kernel@vger.kernel.org;
> linuxarm@openeuler.org
> Subject: Re: [PATCH v10 0/4] debugfs to hisilicon migration driver
> 
> On Thu, Oct 24, 2024 at 01:18:55PM +0000, Shameerali Kolothum Thodi
> 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.
> >
> > Could you please take another look at this series as it looks like almost
> there.
> 
> Why are we so keen to do this? Nobody else needed a complex debugfs for
> their live migration?

I don't think it is that complex debugfs.  Longfang has found this very helpful in
testing and debug with hardware. 

And hopefully this can be expanded in future with different hardware revisions.

Thanks,
Shameer

      reply	other threads:[~2024-10-24 16:06 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 ` [PATCH v10 0/4] debugfs to hisilicon migration driver Shameerali Kolothum Thodi
2024-10-24 15:27   ` Jason Gunthorpe
2024-10-24 16:06     ` Shameerali Kolothum Thodi [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=5d0a9221a3b84ea88d2f77197f913091@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