From: liulongfang <liulongfang@huawei.com>
To: Shameerali Kolothum Thodi <shameerali.kolothum.thodi@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 v8 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver
Date: Thu, 22 Aug 2024 16:29:19 +0800 [thread overview]
Message-ID: <c7f0ae83-9490-c9db-e098-6eb18443599f@huawei.com> (raw)
In-Reply-To: <42784fb0fd1c44cf9470c9662e154b88@huawei.com>
On 2024/8/14 17:39, Shameerali Kolothum Thodi wrote:
>
>
>> -----Original Message-----
>> From: liulongfang <liulongfang@huawei.com>
>> Sent: Tuesday, August 6, 2024 1:29 PM
>> 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 v8 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon
>> migration driver
> ...
>> +static int hisi_acc_vf_dev_read(struct seq_file *seq, void *data)
>> +{
>> + struct device *vf_dev = seq->private;
>> + struct vfio_pci_core_device *core_device = dev_get_drvdata(vf_dev);
>> + struct vfio_device *vdev = &core_device->vdev;
>> + struct hisi_acc_vf_core_device *hisi_acc_vdev =
>> hisi_acc_get_vf_dev(vdev);
>> + size_t vf_data_sz = offsetofend(struct acc_vf_data, padding);
>> + struct acc_vf_data *vf_data = NULL;
>> + int ret;
>> +
>> + vf_data = kzalloc(sizeof(struct acc_vf_data), GFP_KERNEL);
>> + if (!vf_data)
>> + return -ENOMEM;
>> +
>> + mutex_lock(&hisi_acc_vdev->state_mutex);
>> + ret = hisi_acc_vf_debug_check(seq, vdev);
>> + if (ret) {
>> + mutex_unlock(&hisi_acc_vdev->state_mutex);
>> + goto migf_err;
>> + }
>> +
>> + vf_data->vf_qm_state = hisi_acc_vdev->vf_qm_state;
>> + ret = vf_qm_read_data(&hisi_acc_vdev->vf_qm, vf_data);
>> + if (ret) {
>> + mutex_unlock(&hisi_acc_vdev->state_mutex);
>> + goto migf_err;
>> + }
>> +
>> + mutex_unlock(&hisi_acc_vdev->state_mutex);
>> +
>> + seq_hex_dump(seq, "Dev Data:", DUMP_PREFIX_OFFSET, 16, 1,
>> + (unsigned char *)vf_data,
>> + vf_data_sz, false);
>> +
>> + seq_printf(seq,
>> + "acc device:\n"
>> + "device ready: %u\n"
>> + "device opened: %d\n"
>> + "data size: %lu\n",
>> + hisi_acc_vdev->vf_qm_state,
>> + hisi_acc_vdev->dev_opened,
>
> I think the dev_opened will be always true if it reaches here and can be
> removed from here and from hisi_acc_vf_migf_read() as well.
>
> Please don't respin just for this. Let us wait for others to review this.
>
Hello,Alex Williamson and Jason Gunthorpe:
Could you take a moment to review this patch?
Thanks,
Longfang.
> Thanks,
> Shameer
> .
>
next prev parent reply other threads:[~2024-08-22 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 12:29 [PATCH v8 0/4] debugfs to " Longfang Liu
2024-08-06 12:29 ` [PATCH v8 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-08-06 12:29 ` [PATCH v8 2/4] hisi_acc_vfio_pci: create subfunction for data reading Longfang Liu
2024-08-06 12:29 ` [PATCH v8 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-08-14 9:39 ` Shameerali Kolothum Thodi
2024-08-22 8:29 ` liulongfang [this message]
2024-08-26 21:06 ` Alex Williamson
2024-08-27 9:35 ` liulongfang
2024-08-27 11:26 ` liulongfang
2024-08-27 12:41 ` liulongfang
2024-08-06 12:29 ` [PATCH v8 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-08-14 9:35 ` 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=c7f0ae83-9490-c9db-e098-6eb18443599f@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
all inboxes | Powered by JetHome®