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 v6 3/5] hisi_acc_vfio_pci: create subfunction for data reading
Date: Tue, 7 May 2024 16:30:51 +0800 [thread overview]
Message-ID: <77e776eb-bc46-0a07-217c-e3bf385c7502@huawei.com> (raw)
In-Reply-To: <20240503102506.5b7a41ef.alex.williamson@redhat.com>
On 2024/5/4 0:25, Alex Williamson wrote:
> On Thu, 25 Apr 2024 21:23:20 +0800
> Longfang Liu <liulongfang@huawei.com> wrote:
>
>> During the live migration process.
>
> This is not a complete sentence.
>
>> It needs to obtain various status
>> data of drivers and devices.
>
> What's "It" describing here?
>
>> In order to facilitate calling it in the
>> debugfs function.
>
> Also not a complete sentence.
>
>> For all operations that read data from device registers,
>> the driver creates a subfunction.
>
> There's only one sub-function.
>
>> Also fixed the location of address data.
>
> I think this is addressed in the previous patch now? Thanks,
>
OK, I'll update the descriptions again.
> Alex
>
Thanks,
Longfang.
>> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
>> ---
>> .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 54 +++++++++++--------
>> 1 file changed, 33 insertions(+), 21 deletions(-)
>>
>> diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> index 0c7e31076ff4..bf358ba94b5d 100644
>> --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> @@ -486,31 +486,11 @@ static int vf_qm_load_data(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>> return 0;
>> }
>>
>> -static int vf_qm_state_save(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>> - struct hisi_acc_vf_migration_file *migf)
>> +static int vf_qm_read_data(struct hisi_qm *vf_qm, struct acc_vf_data *vf_data)
>> {
>> - struct acc_vf_data *vf_data = &migf->vf_data;
>> - struct hisi_qm *vf_qm = &hisi_acc_vdev->vf_qm;
>> struct device *dev = &vf_qm->pdev->dev;
>> int ret;
>>
>> - if (unlikely(qm_wait_dev_not_ready(vf_qm))) {
>> - /* Update state and return with match data */
>> - vf_data->vf_qm_state = QM_NOT_READY;
>> - hisi_acc_vdev->vf_qm_state = vf_data->vf_qm_state;
>> - migf->total_length = QM_MATCH_SIZE;
>> - return 0;
>> - }
>> -
>> - vf_data->vf_qm_state = QM_READY;
>> - hisi_acc_vdev->vf_qm_state = vf_data->vf_qm_state;
>> -
>> - ret = vf_qm_cache_wb(vf_qm);
>> - if (ret) {
>> - dev_err(dev, "failed to writeback QM Cache!\n");
>> - return ret;
>> - }
>> -
>> ret = qm_get_regs(vf_qm, vf_data);
>> if (ret)
>> return -EINVAL;
>> @@ -536,6 +516,38 @@ static int vf_qm_state_save(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>> return -EINVAL;
>> }
>>
>> + return 0;
>> +}
>> +
>> +static int vf_qm_state_save(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>> + struct hisi_acc_vf_migration_file *migf)
>> +{
>> + struct acc_vf_data *vf_data = &migf->vf_data;
>> + struct hisi_qm *vf_qm = &hisi_acc_vdev->vf_qm;
>> + struct device *dev = &vf_qm->pdev->dev;
>> + int ret;
>> +
>> + if (unlikely(qm_wait_dev_not_ready(vf_qm))) {
>> + /* Update state and return with match data */
>> + vf_data->vf_qm_state = QM_NOT_READY;
>> + hisi_acc_vdev->vf_qm_state = vf_data->vf_qm_state;
>> + migf->total_length = QM_MATCH_SIZE;
>> + return 0;
>> + }
>> +
>> + vf_data->vf_qm_state = QM_READY;
>> + hisi_acc_vdev->vf_qm_state = vf_data->vf_qm_state;
>> +
>> + ret = vf_qm_cache_wb(vf_qm);
>> + if (ret) {
>> + dev_err(dev, "failed to writeback QM Cache!\n");
>> + return ret;
>> + }
>> +
>> + ret = vf_qm_read_data(vf_qm, vf_data);
>> + if (ret)
>> + return -EINVAL;
>> +
>> migf->total_length = sizeof(struct acc_vf_data);
>> return 0;
>> }
>
> .
>
next prev parent reply other threads:[~2024-05-07 8:30 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 [this message]
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
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=77e776eb-bc46-0a07-217c-e3bf385c7502@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).