From: Sricharan R <sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> To: Lorenzo Pieralisi <lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org>, Nate Watterson <nwatters-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> Cc: catalin.marinas-5wv7dgnIgG8@public.gmane.org, will.deacon-5wv7dgnIgG8@public.gmane.org, okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org, frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org, linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, tn-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org, linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, arnd-r2nGTMty4D4@public.gmane.org, linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org, rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, sudeep.holla-5wv7dgnIgG8@public.gmane.org Subject: Re: [PATCH V11 08/11] drivers: acpi: Handle IOMMU lookup failure with deferred probing or error Date: Tue, 23 May 2017 14:31:17 +0530 [thread overview] Message-ID: <c6d5c033-a8f9-03e3-9963-cd291ae2d7e1@codeaurora.org> (raw) In-Reply-To: <20170523085241.GA18204@red-moon> Hi Lorenzo, On 5/23/2017 2:22 PM, Lorenzo Pieralisi wrote: > On Tue, May 23, 2017 at 02:26:10AM -0400, Nate Watterson wrote: >> Hi Sricharan, >> >> On 4/10/2017 7:21 AM, Sricharan R wrote: >>> This is an equivalent to the DT's handling of the iommu master's probe >>> with deferred probing when the corrsponding iommu is not probed yet. >>> The lack of a registered IOMMU can be caused by the lack of a driver for >>> the IOMMU, the IOMMU device probe not having been performed yet, having >>> been deferred, or having failed. >>> >>> The first case occurs when the firmware describes the bus master and >>> IOMMU topology correctly but no device driver exists for the IOMMU yet >>> or the device driver has not been compiled in. Return NULL, the caller >>> will configure the device without an IOMMU. >>> >>> The second and third cases are handled by deferring the probe of the bus >>> master device which will eventually get reprobed after the IOMMU. >>> >>> The last case is currently handled by deferring the probe of the bus >>> master device as well. A mechanism to either configure the bus master >>> device without an IOMMU or to fail the bus master device probe depending >>> on whether the IOMMU is optional or mandatory would be a good >>> enhancement. >>> >>> Tested-by: Hanjun Guo <hanjun.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> >>> Reviewed-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org> >>> [Lorenzo: Added fixes for dma_coherent_mask overflow, acpi_dma_configure >>> called multiple times for same device] >>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org> >>> Signed-off-by: Sricharan R <sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> >>> --- >>> drivers/acpi/arm64/iort.c | 33 ++++++++++++++++++++++++++++++++- >>> drivers/acpi/scan.c | 11 ++++++++--- >>> drivers/base/dma-mapping.c | 2 +- >>> include/acpi/acpi_bus.h | 2 +- >>> include/linux/acpi.h | 7 +++++-- >>> 5 files changed, 47 insertions(+), 8 deletions(-) >>> >>> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c >>> index 3dd9ec3..e323ece 100644 >>> --- a/drivers/acpi/arm64/iort.c >>> +++ b/drivers/acpi/arm64/iort.c >>> @@ -543,6 +543,14 @@ static const struct iommu_ops *iort_iommu_xlate(struct device *dev, >>> const struct iommu_ops *ops = NULL; >>> int ret = -ENODEV; >>> struct fwnode_handle *iort_fwnode; >>> + struct iommu_fwspec *fwspec = dev->iommu_fwspec; >>> + >>> + /* >>> + * If we already translated the fwspec there >>> + * is nothing left to do, return the iommu_ops. >>> + */ >>> + if (fwspec && fwspec->ops) >>> + return fwspec->ops; >> >> Is this logic strictly required? It breaks masters with multiple SIDs >> as only the first SID is actually added to the master's fwspec. > > My bad, that's indeed a silly bug I introduced. Please let me know if the > patch below fixes it, we will send it upstream shortly. > oops, i think emails crossed. Please let me know if you are ok to add this to the other fixes. Regards, Sricharan > Lorenzo > > -- >8 -- > diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c > index c5fecf9..e326f2a 100644 > --- a/drivers/acpi/arm64/iort.c > +++ b/drivers/acpi/arm64/iort.c > @@ -666,14 +666,6 @@ static const struct iommu_ops *iort_iommu_xlate(struct device *dev, > int ret = -ENODEV; > struct fwnode_handle *iort_fwnode; > > - /* > - * If we already translated the fwspec there > - * is nothing left to do, return the iommu_ops. > - */ > - ops = iort_fwspec_iommu_ops(dev->iommu_fwspec); > - if (ops) > - return ops; > - > if (node) { > iort_fwnode = iort_get_fwnode(node); > if (!iort_fwnode) > @@ -735,6 +727,14 @@ const struct iommu_ops *iort_iommu_configure(struct device *dev) > u32 streamid = 0; > int err; > > + /* > + * If we already translated the fwspec there > + * is nothing left to do, return the iommu_ops. > + */ > + ops = iort_fwspec_iommu_ops(dev->iommu_fwspec); > + if (ops) > + return ops; > + > if (dev_is_pci(dev)) { > struct pci_bus *bus = to_pci_dev(dev)->bus; > u32 rid; > > -- "QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: Sricharan R <sricharan@codeaurora.org> To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>, Nate Watterson <nwatters@codeaurora.org> Cc: robin.murphy@arm.com, will.deacon@arm.com, joro@8bytes.org, iommu@lists.linux-foundation.org, linux-arm-kernel@lists.infradead.org, linux-arm-msm@vger.kernel.org, m.szyprowski@samsung.com, bhelgaas@google.com, linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, tn@semihalf.com, hanjun.guo@linaro.org, okaya@codeaurora.org, robh+dt@kernel.org, frowand.list@gmail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, sudeep.holla@arm.com, rjw@rjwysocki.net, lenb@kernel.org, catalin.marinas@arm.com, arnd@arndb.de, linux-arch@vger.kernel.org, gregkh@linuxfoundation.org Subject: Re: [PATCH V11 08/11] drivers: acpi: Handle IOMMU lookup failure with deferred probing or error Date: Tue, 23 May 2017 14:31:17 +0530 [thread overview] Message-ID: <c6d5c033-a8f9-03e3-9963-cd291ae2d7e1@codeaurora.org> (raw) Message-ID: <20170523090117.SDPnAJuMx5jxSi8LhncZ9RuUu_1003mYCgitAgpZc6U@z> (raw) In-Reply-To: <20170523085241.GA18204@red-moon> Hi Lorenzo, On 5/23/2017 2:22 PM, Lorenzo Pieralisi wrote: > On Tue, May 23, 2017 at 02:26:10AM -0400, Nate Watterson wrote: >> Hi Sricharan, >> >> On 4/10/2017 7:21 AM, Sricharan R wrote: >>> This is an equivalent to the DT's handling of the iommu master's probe >>> with deferred probing when the corrsponding iommu is not probed yet. >>> The lack of a registered IOMMU can be caused by the lack of a driver for >>> the IOMMU, the IOMMU device probe not having been performed yet, having >>> been deferred, or having failed. >>> >>> The first case occurs when the firmware describes the bus master and >>> IOMMU topology correctly but no device driver exists for the IOMMU yet >>> or the device driver has not been compiled in. Return NULL, the caller >>> will configure the device without an IOMMU. >>> >>> The second and third cases are handled by deferring the probe of the bus >>> master device which will eventually get reprobed after the IOMMU. >>> >>> The last case is currently handled by deferring the probe of the bus >>> master device as well. A mechanism to either configure the bus master >>> device without an IOMMU or to fail the bus master device probe depending >>> on whether the IOMMU is optional or mandatory would be a good >>> enhancement. >>> >>> Tested-by: Hanjun Guo <hanjun.guo@linaro.org> >>> Reviewed-by: Robin Murphy <robin.murphy@arm.com> >>> [Lorenzo: Added fixes for dma_coherent_mask overflow, acpi_dma_configure >>> called multiple times for same device] >>> Signed-off-by: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> >>> Signed-off-by: Sricharan R <sricharan@codeaurora.org> >>> --- >>> drivers/acpi/arm64/iort.c | 33 ++++++++++++++++++++++++++++++++- >>> drivers/acpi/scan.c | 11 ++++++++--- >>> drivers/base/dma-mapping.c | 2 +- >>> include/acpi/acpi_bus.h | 2 +- >>> include/linux/acpi.h | 7 +++++-- >>> 5 files changed, 47 insertions(+), 8 deletions(-) >>> >>> diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c >>> index 3dd9ec3..e323ece 100644 >>> --- a/drivers/acpi/arm64/iort.c >>> +++ b/drivers/acpi/arm64/iort.c >>> @@ -543,6 +543,14 @@ static const struct iommu_ops *iort_iommu_xlate(struct device *dev, >>> const struct iommu_ops *ops = NULL; >>> int ret = -ENODEV; >>> struct fwnode_handle *iort_fwnode; >>> + struct iommu_fwspec *fwspec = dev->iommu_fwspec; >>> + >>> + /* >>> + * If we already translated the fwspec there >>> + * is nothing left to do, return the iommu_ops. >>> + */ >>> + if (fwspec && fwspec->ops) >>> + return fwspec->ops; >> >> Is this logic strictly required? It breaks masters with multiple SIDs >> as only the first SID is actually added to the master's fwspec. > > My bad, that's indeed a silly bug I introduced. Please let me know if the > patch below fixes it, we will send it upstream shortly. > oops, i think emails crossed. Please let me know if you are ok to add this to the other fixes. Regards, Sricharan > Lorenzo > > -- >8 -- > diff --git a/drivers/acpi/arm64/iort.c b/drivers/acpi/arm64/iort.c > index c5fecf9..e326f2a 100644 > --- a/drivers/acpi/arm64/iort.c > +++ b/drivers/acpi/arm64/iort.c > @@ -666,14 +666,6 @@ static const struct iommu_ops *iort_iommu_xlate(struct device *dev, > int ret = -ENODEV; > struct fwnode_handle *iort_fwnode; > > - /* > - * If we already translated the fwspec there > - * is nothing left to do, return the iommu_ops. > - */ > - ops = iort_fwspec_iommu_ops(dev->iommu_fwspec); > - if (ops) > - return ops; > - > if (node) { > iort_fwnode = iort_get_fwnode(node); > if (!iort_fwnode) > @@ -735,6 +727,14 @@ const struct iommu_ops *iort_iommu_configure(struct device *dev) > u32 streamid = 0; > int err; > > + /* > + * If we already translated the fwspec there > + * is nothing left to do, return the iommu_ops. > + */ > + ops = iort_fwspec_iommu_ops(dev->iommu_fwspec); > + if (ops) > + return ops; > + > if (dev_is_pci(dev)) { > struct pci_bus *bus = to_pci_dev(dev)->bus; > u32 rid; > > -- "QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2017-05-23 9:01 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <CGME20170410112136epcas2p2cdd7dc21a8dc0ffcfab7f8290c4b7467@epcas2p2.samsung.com> 2017-04-10 11:20 ` [PATCH V11 00/11] IOMMU probe deferral support Sricharan R 2017-04-10 11:20 ` Sricharan R 2017-04-10 11:20 ` [PATCH V11 01/11] iommu/of: Refactor of_iommu_configure() for error handling Sricharan R 2017-04-10 11:20 ` [PATCH V11 02/11] iommu/of: Prepare for deferred IOMMU configuration Sricharan R 2017-04-10 11:20 ` Sricharan R 2017-04-10 11:20 ` [PATCH V11 03/11] of: dma: Make of_dma_deconfigure() public Sricharan R 2017-04-10 11:20 ` Sricharan R 2017-04-10 11:20 ` [PATCH V11 04/11] ACPI/IORT: Add function to check SMMUs drivers presence Sricharan R 2017-04-10 11:20 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 05/11] of: device: Fix overflow of coherent_dma_mask Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-10 11:56 ` [PATCH V11 00/11] IOMMU probe deferral support Frank Rowand 2017-04-10 11:56 ` Frank Rowand [not found] ` <1491823266-1209-1-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2017-04-10 11:21 ` [PATCH V11 06/11] of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 07/11] iommu: of: Handle IOMMU lookup failure with deferred probing or error Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 08/11] drivers: acpi: " Sricharan R 2017-04-10 11:21 ` Sricharan R [not found] ` <1491823266-1209-9-git-send-email-sricharan-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2017-05-23 6:26 ` Nate Watterson 2017-05-23 6:26 ` Nate Watterson [not found] ` <41668eff-271c-1c4c-7665-3bf0faa74669-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2017-05-23 8:52 ` Lorenzo Pieralisi 2017-05-23 8:52 ` Lorenzo Pieralisi 2017-05-23 9:01 ` Sricharan R [this message] 2017-05-23 9:01 ` Sricharan R [not found] ` <c6d5c033-a8f9-03e3-9963-cd291ae2d7e1-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org> 2017-05-23 9:26 ` Lorenzo Pieralisi 2017-05-23 9:26 ` Lorenzo Pieralisi 2017-05-23 11:27 ` Nate Watterson 2017-05-23 11:27 ` Nate Watterson 2017-05-23 8:59 ` Sricharan R 2017-05-23 8:59 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 09/11] arm64: dma-mapping: Remove the notifier trick to handle early setting of dma_ops Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 10/11] iommu/arm-smmu: Clean up early-probing workarounds Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-10 11:21 ` [PATCH V11 11/11] ACPI/IORT: Remove linker section for IORT entries probing Sricharan R 2017-04-10 11:21 ` Sricharan R 2017-04-20 14:31 ` [PATCH V11 00/11] IOMMU probe deferral support Joerg Roedel 2017-04-20 14:31 ` Joerg Roedel 2017-05-08 11:23 ` Marek Szyprowski 2017-05-08 11:23 ` Marek Szyprowski 2017-05-08 14:57 ` Sricharan R 2017-05-08 14:57 ` Sricharan R
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=c6d5c033-a8f9-03e3-9963-cd291ae2d7e1@codeaurora.org \ --to=sricharan-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \ --cc=arnd-r2nGTMty4D4@public.gmane.org \ --cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \ --cc=catalin.marinas-5wv7dgnIgG8@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=frowand.list-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \ --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \ --cc=lenb-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \ --cc=linux-arm-msm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=lorenzo.pieralisi-5wv7dgnIgG8@public.gmane.org \ --cc=nwatters-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \ --cc=okaya-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \ --cc=rjw-LthD3rsA81gm4RdzfppkhA@public.gmane.org \ --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=sudeep.holla-5wv7dgnIgG8@public.gmane.org \ --cc=tn-nYOzD4b6Jr9Wk0Htik3J/w@public.gmane.org \ --cc=will.deacon-5wv7dgnIgG8@public.gmane.org \ /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: linkBe 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 NNTP newsgroup(s).