LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: Robin Murphy <robin.murphy@arm.com>, sebott@linux.vnet.ibm.com
Cc: linux-s390@vger.kernel.org, pasic@linux.vnet.ibm.com,
alex.williamson@redhat.com, kvm@vger.kernel.org,
heiko.carstens@de.ibm.com, walling@linux.ibm.com,
linux-kernel@vger.kernel.org, borntraeger@de.ibm.com,
iommu@lists.linux-foundation.org, schwidefsky@de.ibm.com,
gerald.schaefer@de.ibm.com
Subject: Re: [PATCH 1/4] s390: pci: Exporting access to CLP PCI function and PCI group
Date: Fri, 10 May 2019 16:45:15 +0200 [thread overview]
Message-ID: <289bdf82-75ba-4ba4-9362-dd8fc721cfc8@linux.ibm.com> (raw)
In-Reply-To: <a06ffd83-5fde-8c6e-b25b-bd4163d4cd5f@arm.com>
On 10/05/2019 12:21, Robin Murphy wrote:
> On 10/05/2019 09:22, Pierre Morel wrote:
>> For the generic implementation of VFIO PCI we need to retrieve
>> the hardware configuration for the PCI functions and the
>> PCI function groups.
>>
>> We modify the internal function using CLP Query PCI function and
>> CLP query PCI function group so that they can be called from
>> outside the S390 architecture PCI code and prefix the two
>> functions with "zdev" to make clear that they can be called
>> knowing only the associated zdevice.
>>
>> Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
>> Reviewed-by: Sebastian Ott <sebott@linux.ibm.com>
>> ---
>> arch/s390/include/asm/pci.h | 3 ++
>> arch/s390/pci/pci_clp.c | 72
>> ++++++++++++++++++++++++---------------------
>> 2 files changed, 41 insertions(+), 34 deletions(-)
>>
>> diff --git a/arch/s390/include/asm/pci.h b/arch/s390/include/asm/pci.h
>> index 305befd..e66b246 100644
>> --- a/arch/s390/include/asm/pci.h
>> +++ b/arch/s390/include/asm/pci.h
>> @@ -261,4 +261,7 @@ cpumask_of_pcibus(const struct pci_bus *bus)
>> #endif /* CONFIG_NUMA */
>> +int zdev_query_pci_fngrp(struct zpci_dev *zdev,
>> + struct clp_req_rsp_query_pci_grp *rrb);
>> +int zdev_query_pci_fn(struct zpci_dev *zdev, struct
>> clp_req_rsp_query_pci *rrb);
>> #endif
>> diff --git a/arch/s390/pci/pci_clp.c b/arch/s390/pci/pci_clp.c
>> index 3a36b07..4ae5d77 100644
>> --- a/arch/s390/pci/pci_clp.c
>> +++ b/arch/s390/pci/pci_clp.c
>> @@ -113,32 +113,18 @@ static void clp_store_query_pci_fngrp(struct
>> zpci_dev *zdev,
>> }
>> }
>> -static int clp_query_pci_fngrp(struct zpci_dev *zdev, u8 pfgid)
>> +int zdev_query_pci_fngrp(struct zpci_dev *zdev,
>> + struct clp_req_rsp_query_pci_grp *rrb)
>> {
>> - struct clp_req_rsp_query_pci_grp *rrb;
>> - int rc;
>> -
>> - rrb = clp_alloc_block(GFP_KERNEL);
>> - if (!rrb)
>> - return -ENOMEM;
>> -
>> memset(rrb, 0, sizeof(*rrb));
>> rrb->request.hdr.len = sizeof(rrb->request);
>> rrb->request.hdr.cmd = CLP_QUERY_PCI_FNGRP;
>> rrb->response.hdr.len = sizeof(rrb->response);
>> - rrb->request.pfgid = pfgid;
>> + rrb->request.pfgid = zdev->pfgid;
>> - rc = clp_req(rrb, CLP_LPS_PCI);
>> - if (!rc && rrb->response.hdr.rsp == CLP_RC_OK)
>> - clp_store_query_pci_fngrp(zdev, &rrb->response);
>> - else {
>> - zpci_err("Q PCI FGRP:\n");
>> - zpci_err_clp(rrb->response.hdr.rsp, rc);
>> - rc = -EIO;
>> - }
>> - clp_free_block(rrb);
>> - return rc;
>> + return clp_req(rrb, CLP_LPS_PCI);
>> }
>> +EXPORT_SYMBOL(zdev_query_pci_fngrp);
>
> AFAICS it's only the IOMMU driver itself which needs to call these. That
> can't be built as a module, so you shouldn't need explicit exports - the
> header declaration is enough.
>
> Robin.
This is right and seeing the pointer type only zPCI and s390iommu can
make use of it.
If nobody has another point of view I will remove the export on the
next iteration.
Thanks,
Pierre
>
>> static int clp_store_query_pci_fn(struct zpci_dev *zdev,
>> struct clp_rsp_query_pci *response)
>> @@ -174,32 +160,50 @@ static int clp_store_query_pci_fn(struct
>> zpci_dev *zdev,
>> return 0;
>> }
>> -static int clp_query_pci_fn(struct zpci_dev *zdev, u32 fh)
>> +int zdev_query_pci_fn(struct zpci_dev *zdev, struct
>> clp_req_rsp_query_pci *rrb)
>> +{
>> +
>> + memset(rrb, 0, sizeof(*rrb));
>> + rrb->request.hdr.len = sizeof(rrb->request);
>> + rrb->request.hdr.cmd = CLP_QUERY_PCI_FN;
>> + rrb->response.hdr.len = sizeof(rrb->response);
>> + rrb->request.fh = zdev->fh;
>> +
>> + return clp_req(rrb, CLP_LPS_PCI);
>> +}
>> +EXPORT_SYMBOL(zdev_query_pci_fn);
>> +
>> +static int clp_query_pci(struct zpci_dev *zdev)
>> {
>> struct clp_req_rsp_query_pci *rrb;
>> + struct clp_req_rsp_query_pci_grp *grrb;
>> int rc;
>> rrb = clp_alloc_block(GFP_KERNEL);
>> if (!rrb)
>> return -ENOMEM;
>> - memset(rrb, 0, sizeof(*rrb));
>> - rrb->request.hdr.len = sizeof(rrb->request);
>> - rrb->request.hdr.cmd = CLP_QUERY_PCI_FN;
>> - rrb->response.hdr.len = sizeof(rrb->response);
>> - rrb->request.fh = fh;
>> -
>> - rc = clp_req(rrb, CLP_LPS_PCI);
>> - if (!rc && rrb->response.hdr.rsp == CLP_RC_OK) {
>> - rc = clp_store_query_pci_fn(zdev, &rrb->response);
>> - if (rc)
>> - goto out;
>> - rc = clp_query_pci_fngrp(zdev, rrb->response.pfgid);
>> - } else {
>> + rc = zdev_query_pci_fn(zdev, rrb);
>> + if (rc || rrb->response.hdr.rsp != CLP_RC_OK) {
>> zpci_err("Q PCI FN:\n");
>> zpci_err_clp(rrb->response.hdr.rsp, rc);
>> rc = -EIO;
>> + goto out;
>> }
>> + rc = clp_store_query_pci_fn(zdev, &rrb->response);
>> + if (rc)
>> + goto out;
>> +
>> + grrb = (struct clp_req_rsp_query_pci_grp *)rrb;
>> + rc = zdev_query_pci_fngrp(zdev, grrb);
>> + if (rc || grrb->response.hdr.rsp != CLP_RC_OK) {
>> + zpci_err("Q PCI FGRP:\n");
>> + zpci_err_clp(grrb->response.hdr.rsp, rc);
>> + rc = -EIO;
>> + goto out;
>> + }
>> + clp_store_query_pci_fngrp(zdev, &grrb->response);
>> +
>> out:
>> clp_free_block(rrb);
>> return rc;
>> @@ -219,7 +223,7 @@ int clp_add_pci_device(u32 fid, u32 fh, int
>> configured)
>> zdev->fid = fid;
>> /* Query function properties and update zdev */
>> - rc = clp_query_pci_fn(zdev, fh);
>> + rc = clp_query_pci(zdev);
>> if (rc)
>> goto error;
>>
>
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2019-05-10 14:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 8:22 [PATCH 0/4] Retrieving zPCI specific info with VFIO Pierre Morel
2019-05-10 8:22 ` [PATCH 1/4] s390: pci: Exporting access to CLP PCI function and PCI group Pierre Morel
2019-05-10 10:21 ` Robin Murphy
2019-05-10 14:45 ` Pierre Morel [this message]
2019-05-10 8:22 ` [PATCH 2/4] vfio: vfio_iommu_type1: Define VFIO_IOMMU_INFO_CAPABILITIES Pierre Morel
2019-05-16 14:57 ` Christian Borntraeger
2019-05-16 18:54 ` Alex Williamson
2019-05-16 18:31 ` Alex Williamson
2019-05-17 8:18 ` Pierre Morel
2019-05-10 8:22 ` [PATCH 3/4] s390: iommu: Adding get attributes for s390_iommu Pierre Morel
2019-05-10 8:22 ` [PATCH 4/4] vfio: vfio_iommu_type1: implement VFIO_IOMMU_INFO_CAPABILITIES Pierre Morel
2019-05-16 18:40 ` Alex Williamson
2019-05-17 8:17 ` Pierre Morel
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=289bdf82-75ba-4ba4-9362-dd8fc721cfc8@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=robin.murphy@arm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sebott@linux.vnet.ibm.com \
--cc=walling@linux.ibm.com \
--subject='Re: [PATCH 1/4] s390: pci: Exporting access to CLP PCI function and PCI group' \
/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
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 NNTP newsgroup(s).