From: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>,
liulongfang <liulongfang@huawei.com>
Cc: "jgg@nvidia.com" <jgg@nvidia.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 v6 4/5] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver
Date: Tue, 7 May 2024 08:06:04 +0000 [thread overview]
Message-ID: <7b0645b43889431b9830bc17835c15e4@huawei.com> (raw)
In-Reply-To: <20240503112120.3740da24.alex.williamson@redhat.com>
> -----Original Message-----
> From: Alex Williamson <alex.williamson@redhat.com>
> Sent: Friday, May 3, 2024 6:21 PM
> To: liulongfang <liulongfang@huawei.com>
> Cc: jgg@nvidia.com; Shameerali Kolothum Thodi
> <shameerali.kolothum.thodi@huawei.com>; Jonathan Cameron
> <jonathan.cameron@huawei.com>; kvm@vger.kernel.org; linux-
> kernel@vger.kernel.org; linuxarm@openeuler.org
> Subject: Re: [PATCH v6 4/5] hisi_acc_vfio_pci: register debugfs for hisilicon
> migration driver
>
> On Thu, 25 Apr 2024 21:23:21 +0800
> Longfang Liu <liulongfang@huawei.com> wrote:
>
> > On the debugfs framework of VFIO, if the CONFIG_VFIO_DEBUGFS macro is
> > enabled, the debug function is registered for the live migration driver
> > of the HiSilicon accelerator device.
> >
> > After registering the HiSilicon accelerator device on the debugfs
> > framework of live migration of vfio, a directory file "hisi_acc"
> > of debugfs is created, and then three debug function files are
> > created in this directory:
> >
> > vfio
> > |
> > +---<dev_name1>
> > | +---migration
> > | +--state
> > | +--hisi_acc
> > | +--dev_data
> > | +--migf_data
> > | +--cmd_state
> > |
> > +---<dev_name2>
> > +---migration
> > +--state
> > +--hisi_acc
> > +--dev_data
> > +--migf_data
> > +--cmd_state
> >
> > dev_data file: read device data that needs to be migrated from the
> > current device in real time
> > migf_data file: read the migration data of the last live migration
> > from the current driver.
> > cmd_state: used to get the cmd channel state for the device.
> >
> > +----------------+ +--------------+ +---------------+
> > | migration dev | | src dev | | dst dev |
> > +-------+--------+ +------+-------+ +-------+-------+
> > | | |
> > | +------v-------+ +-------v-------+
> > | | saving_mif | | resuming_migf |
> > read | | file | | file |
> > | +------+-------+ +-------+-------+
> > | | copy |
> > | +------------+----------+
> > | |
> > +-------v---------+ +-------v--------+
> > | data buffer | | debug_migf |
> > +-------+---------+ +-------+--------+
> > | |
> > cat | cat |
> > +-------v--------+ +-------v--------+
> > | dev_data | | migf_data |
> > +----------------+ +----------------+
> >
> > When accessing debugfs, user can obtain the real-time status data
> > of the device through the "dev_data" file. It will directly read
> > the device status data and will not affect the live migration
> > function. Its data is stored in the allocated memory buffer,
> > and the memory is released after data returning to user mode.
> >
> > To obtain the data of the last complete migration, user need to
> > obtain it through the "migf_data" file. Since the live migration
> > data only exists during the migration process, it is destroyed
> > after the migration is completed.
> > In order to save this data, a debug_migf file is created in the
> > driver. At the end of the live migration process, copy the data
> > to debug_migf.
> >
> > Signed-off-by: Longfang Liu <liulongfang@huawei.com>
> > ---
> > .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 225 ++++++++++++++++++
> > .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h | 7 +
> > 2 files changed, 232 insertions(+)
> >
> > diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> > index bf358ba94b5d..656b3d975940 100644
> > --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> > +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
> > @@ -627,15 +627,33 @@ static void hisi_acc_vf_disable_fd(struct
> hisi_acc_vf_migration_file *migf)
> > mutex_unlock(&migf->lock);
> > }
> >
> > +static void hisi_acc_debug_migf_copy(struct hisi_acc_vf_core_device
> *hisi_acc_vdev,
> > + struct hisi_acc_vf_migration_file *src_migf)
> > +{
> > + struct hisi_acc_vf_migration_file *dst_migf = hisi_acc_vdev-
> >debug_migf;
> > +
> > + if (!dst_migf)
> > + return;
> > +
> > + mutex_lock(&hisi_acc_vdev->enable_mutex);
> > + dst_migf->disabled = src_migf->disabled;
> > + dst_migf->total_length = src_migf->total_length;
> > + memcpy(&dst_migf->vf_data, &src_migf->vf_data,
> > + sizeof(struct acc_vf_data));
> > + mutex_unlock(&hisi_acc_vdev->enable_mutex);
> > +}
> > +
> > static void hisi_acc_vf_disable_fds(struct hisi_acc_vf_core_device
> *hisi_acc_vdev)
> > {
> > if (hisi_acc_vdev->resuming_migf) {
> > + hisi_acc_debug_migf_copy(hisi_acc_vdev, hisi_acc_vdev-
> >resuming_migf);
> > hisi_acc_vf_disable_fd(hisi_acc_vdev->resuming_migf);
> > fput(hisi_acc_vdev->resuming_migf->filp);
> > hisi_acc_vdev->resuming_migf = NULL;
> > }
> >
> > if (hisi_acc_vdev->saving_migf) {
> > + hisi_acc_debug_migf_copy(hisi_acc_vdev, hisi_acc_vdev-
> >saving_migf);
> > hisi_acc_vf_disable_fd(hisi_acc_vdev->saving_migf);
> > fput(hisi_acc_vdev->saving_migf->filp);
> > hisi_acc_vdev->saving_migf = NULL;
> > @@ -1144,6 +1162,7 @@ static int hisi_acc_vf_qm_init(struct
> hisi_acc_vf_core_device *hisi_acc_vdev)
> > if (!vf_qm->io_base)
> > return -EIO;
> >
> > + mutex_init(&hisi_acc_vdev->enable_mutex);
> > vf_qm->fun_type = QM_HW_VF;
> > vf_qm->pdev = vf_dev;
> > mutex_init(&vf_qm->mailbox_lock);
> > @@ -1294,6 +1313,203 @@ static long hisi_acc_vfio_pci_ioctl(struct
> vfio_device *core_vdev, unsigned int
> > return vfio_pci_core_ioctl(core_vdev, cmd, arg);
> > }
> >
> > +static int hisi_acc_vf_debug_check(struct seq_file *seq, struct vfio_device
> *vdev)
> > +{
> > + struct hisi_acc_vf_core_device *hisi_acc_vdev =
> hisi_acc_get_vf_dev(vdev);
> > + struct hisi_qm *vf_qm = &hisi_acc_vdev->vf_qm;
> > + struct device *dev = vdev->dev;
> > + int ret;
> > +
> > + if (!vdev->mig_ops) {
> > + dev_err(dev, "device does not support live migration!\n");
>
> Sorry, every error path should not spam dmesg with dev_err(). I'm
> going to wait until your co-maintainer approves this before looking at
> any further iterations of this series. Thanks,
Sure. I will sync up with Longfang and also make sure we address all the existing
comments on this before posting the next revision.
Thanks,
Shameer
next prev parent reply other threads:[~2024-05-07 8:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 13:23 [PATCH v6 0/5] add debugfs to hisilicon migration driver Longfang Liu
2024-04-25 13:23 ` [PATCH v6 1/5] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-04-25 13:23 ` [PATCH v6 2/5] hisi_acc_vfio_pci: modify the register location of the XQC address Longfang Liu
2024-05-03 16:11 ` Alex Williamson
2024-05-07 8:29 ` liulongfang
2024-05-07 11:10 ` Shameerali Kolothum Thodi
2024-05-07 12:35 ` Alex Williamson
2024-05-08 7:18 ` liulongfang
2024-05-08 17:59 ` Alex Williamson
2024-05-09 9:37 ` Shameerali Kolothum Thodi
2024-05-09 14:29 ` Alex Williamson
[not found] ` <e63c0c85-7f3a-100c-5059-322268b3f517@huawei.com>
2024-05-13 8:35 ` Shameerali Kolothum Thodi
2024-04-25 13:23 ` [PATCH v6 3/5] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-05-03 16:25 ` Alex Williamson
2024-05-07 8:30 ` liulongfang
2024-04-25 13:23 ` [PATCH v6 4/5] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-05-03 17:21 ` Alex Williamson
2024-05-07 8:06 ` Shameerali Kolothum Thodi [this message]
2024-04-25 13:23 ` [PATCH v6 5/5] Documentation: add debugfs description for hisi migration Longfang Liu
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=7b0645b43889431b9830bc17835c15e4@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