mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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,
	"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH v4 2/4] hisi_acc_vfio_pci: Create subfunction for data reading
Date: Fri, 12 Apr 2024 11:07:00 +0800	[thread overview]
Message-ID: <f1ffdcc6-e74b-bf6c-bddb-73debd78900b@huawei.com> (raw)
In-Reply-To: <20240404140731.2b75cb80.alex.williamson@redhat.com>

On 2024/4/5 4:07, Alex Williamson wrote:
> On Tue, 2 Apr 2024 11:24:30 +0800
> Longfang Liu <liulongfang@huawei.com> wrote:
> 
>> During the live migration process. It needs to obtain various status
>> data of drivers and devices. In order to facilitate calling it in the
>> debugfs function. For all operations that read data from device registers,
>> the driver creates a subfunction.
>> Also fixed the location of address data.
> 
> Cédric noted privately and I agree, 1) fixes should be provided in
> separate patches with a Fixes: tag rather than subtly included in a
> minor refactoring, and 2) what does this imply about the existing
> functionality of migration?  This would seem to suggest existing
> migration data is bogus if we're offset by a register reading the DMA
> address.  The commit log for the Fixes patch should describe this.
>

Okay, the modification of the DMA address offset part is split into
a new patch, and the modification of this part is explained clearly.

Thanks,
Longfang.

>>
>> Signed-off-by: Longfang Liu <liulongfang@huawei.com>
>> ---
>>  .../vfio/pci/hisilicon/hisi_acc_vfio_pci.c    | 56 +++++++++++--------
>>  .../vfio/pci/hisilicon/hisi_acc_vfio_pci.h    |  3 +
>>  2 files changed, 37 insertions(+), 22 deletions(-)
>>
>> diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> index 45351be8e270..bf358ba94b5d 100644
>> --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c
>> @@ -486,6 +486,39 @@ static int vf_qm_load_data(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>>  	return 0;
>>  }
>>  
>> +static int vf_qm_read_data(struct hisi_qm *vf_qm, struct acc_vf_data *vf_data)
>> +{
>> +	struct device *dev = &vf_qm->pdev->dev;
>> +	int ret;
>> +
>> +	ret = qm_get_regs(vf_qm, vf_data);
>> +	if (ret)
>> +		return -EINVAL;
>> +
>> +	/* Every reg is 32 bit, the dma address is 64 bit. */
>> +	vf_data->eqe_dma = vf_data->qm_eqc_dw[QM_XQC_ADDR_HIGH];
>> +	vf_data->eqe_dma <<= QM_XQC_ADDR_OFFSET;
>> +	vf_data->eqe_dma |= vf_data->qm_eqc_dw[QM_XQC_ADDR_LOW];
>> +	vf_data->aeqe_dma = vf_data->qm_aeqc_dw[QM_XQC_ADDR_HIGH];
>> +	vf_data->aeqe_dma <<= QM_XQC_ADDR_OFFSET;
>> +	vf_data->aeqe_dma |= vf_data->qm_aeqc_dw[QM_XQC_ADDR_LOW];
>> +
>> +	/* Through SQC_BT/CQC_BT to get sqc and cqc address */
>> +	ret = qm_get_sqc(vf_qm, &vf_data->sqc_dma);
>> +	if (ret) {
>> +		dev_err(dev, "failed to read SQC addr!\n");
>> +		return -EINVAL;
>> +	}
>> +
>> +	ret = qm_get_cqc(vf_qm, &vf_data->cqc_dma);
>> +	if (ret) {
>> +		dev_err(dev, "failed to read CQC addr!\n");
>> +		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)
>>  {
>> @@ -511,31 +544,10 @@ static int vf_qm_state_save(struct hisi_acc_vf_core_device *hisi_acc_vdev,
>>  		return ret;
>>  	}
>>  
>> -	ret = qm_get_regs(vf_qm, vf_data);
>> +	ret = vf_qm_read_data(vf_qm, vf_data);
>>  	if (ret)
>>  		return -EINVAL;
>>  
>> -	/* Every reg is 32 bit, the dma address is 64 bit. */
>> -	vf_data->eqe_dma = vf_data->qm_eqc_dw[1];
>> -	vf_data->eqe_dma <<= QM_XQC_ADDR_OFFSET;
>> -	vf_data->eqe_dma |= vf_data->qm_eqc_dw[0];
>> -	vf_data->aeqe_dma = vf_data->qm_aeqc_dw[1];
>> -	vf_data->aeqe_dma <<= QM_XQC_ADDR_OFFSET;
>> -	vf_data->aeqe_dma |= vf_data->qm_aeqc_dw[0];
>> -
>> -	/* Through SQC_BT/CQC_BT to get sqc and cqc address */
>> -	ret = qm_get_sqc(vf_qm, &vf_data->sqc_dma);
>> -	if (ret) {
>> -		dev_err(dev, "failed to read SQC addr!\n");
>> -		return -EINVAL;
>> -	}
>> -
>> -	ret = qm_get_cqc(vf_qm, &vf_data->cqc_dma);
>> -	if (ret) {
>> -		dev_err(dev, "failed to read CQC addr!\n");
>> -		return -EINVAL;
>> -	}
>> -
>>  	migf->total_length = sizeof(struct acc_vf_data);
>>  	return 0;
>>  }
>> diff --git a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.h b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.h
>> index 5bab46602fad..7a9dc87627cd 100644
>> --- a/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.h
>> +++ b/drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.h
>> @@ -38,6 +38,9 @@
>>  #define QM_REG_ADDR_OFFSET	0x0004
>>  
>>  #define QM_XQC_ADDR_OFFSET	32U
>> +#define QM_XQC_ADDR_LOW		0x1
>> +#define QM_XQC_ADDR_HIGH	0x2
>> +
>>  #define QM_VF_AEQ_INT_MASK	0x0004
>>  #define QM_VF_EQ_INT_MASK	0x000c
>>  #define QM_IFC_INT_SOURCE_V	0x0020
> 
> .
> 

  reply	other threads:[~2024-04-12  3:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  3:24 [PATCH v4 0/4] add debugfs to hisilicon migration driver Longfang Liu
2024-04-02  3:24 ` [PATCH v4 1/4] hisi_acc_vfio_pci: extract public functions for container_of Longfang Liu
2024-04-02  3:24 ` [PATCH v4 2/4] hisi_acc_vfio_pci: Create subfunction for data reading Longfang Liu
2024-04-04 20:07   ` Alex Williamson
2024-04-12  3:07     ` liulongfang [this message]
2024-04-02  3:24 ` [PATCH v4 3/4] hisi_acc_vfio_pci: register debugfs for hisilicon migration driver Longfang Liu
2024-04-04 20:07   ` Alex Williamson
2024-04-12  8:15     ` liulongfang
2024-04-24  3:15       ` liulongfang
2024-04-02  3:24 ` [PATCH v4 4/4] Documentation: add debugfs description for hisi migration Longfang Liu
2024-04-04 20:07   ` Alex Williamson
2024-04-12  3:02     ` liulongfang

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=f1ffdcc6-e74b-bf6c-bddb-73debd78900b@huawei.com \
    --to=liulongfang@huawei.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@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®