From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 04/16] drivers: iommu: make of_iommu_set/get_ops() DT agnostic
Date: Mon, 14 Nov 2016 10:26:54 +0000 [thread overview]
Message-ID: <20161114102654.GA1677@red-moon> (raw)
In-Reply-To: <33769e3c-265f-6e89-adf9-6d35b1e03579@arm.com>
Hi Robin, Joerg,
On Fri, Nov 11, 2016 at 05:43:39PM +0000, Robin Murphy wrote:
> On 11/11/16 16:27, Joerg Roedel wrote:
> > On Fri, Nov 11, 2016 at 04:17:37PM +0000, Robin Murphy wrote:
> >> In the original of_iommu_configure design, the thought was that an ops
> >> structure could be IOMMU-instance-specific (hence the later-removed
> >> "priv" member), so I suppose right now it is mostly a hangover from
> >> that. However, it's also what we initialise a device's fwspec with, so
> >> becomes important again if we're ever going to get past the limitations
> >> of buses-which-are-not-actually-buses[1].
> >
> > Yeah, I discussed this with a few others at LPC. My current idea is to
> > tell the iommu-core which hardware-iommus exist in the system and a
> > seperate iommu_ops ptr for each of them. Then every struct device can
> > link to the iommu-instance it is translated by.
>
> Er, that sounds very much like a description of what we already have in
> 4.9-rc. Every struct device now has an iommu_fwspec which encapsulates
> both an iommu_ops pointer (which can perfectly well be per-instance if
> the IOMMU driver wants) and a place for the IOMMU-private data to
> replace the mess of archdata.iommu and driver-internal globals.
>
> > We are not there yet, but this will give you the same per-device
> > iommu-ops as implemented here.
>
> With those two patches I linked to, which make the bulk of the IOMMU
> core code per-device-ops-aware off the bat, I'd say we *are* already
> pretty much there. It's only iommu_domain_alloc() which needs a
> device-based alternative, and the non-of_xlate-based IOMMU drivers to
> either call iommu_fwspec_init() for themselves, or perhaps for x86
> plumbing in DMAR/IVRS equivalents of the IORT parsing to the
> infrastructure provided by this series.
I think it all boils down to how we end up implementing the per-device
iommu_ops look-up/binding, question is what do you want me to do with
this patch, it should be fine to drop it and use dev->bus->iommu_ops
for the look-up but I should know sooner rather than later to make
sure the series get another good round of testing.
Please let me know, thank you very much.
Lorenzo
next prev parent reply other threads:[~2016-11-14 10:26 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 14:19 [PATCH v7 00/16] ACPI IORT ARM SMMU support Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 01/16] drivers: acpi: add FWNODE_ACPI_STATIC fwnode type Lorenzo Pieralisi
2016-11-09 23:37 ` Rafael J. Wysocki
2016-11-09 14:19 ` [PATCH v7 02/16] drivers: acpi: iort: introduce linker section for IORT entries probing Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 03/16] drivers: acpi: iort: add support for IOMMU fwnode registration Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 04/16] drivers: iommu: make of_iommu_set/get_ops() DT agnostic Lorenzo Pieralisi
2016-11-09 14:40 ` Robin Murphy
2016-11-10 11:05 ` Lorenzo Pieralisi
2016-11-11 15:22 ` Joerg Roedel
2016-11-11 16:17 ` Robin Murphy
2016-11-11 16:27 ` Joerg Roedel
2016-11-11 17:43 ` Robin Murphy
2016-11-14 10:26 ` Lorenzo Pieralisi [this message]
2016-11-14 12:00 ` Robin Murphy
2016-11-14 15:52 ` Joerg Roedel
2016-11-14 16:42 ` Lorenzo Pieralisi
2016-11-14 18:25 ` Robin Murphy
2016-11-15 10:07 ` Lorenzo Pieralisi
2016-11-16 9:56 ` Lorenzo Pieralisi
2016-11-29 16:05 ` Joerg Roedel
2016-11-29 17:06 ` Will Deacon
2016-11-09 14:19 ` [PATCH v7 05/16] drivers: iommu: arm-smmu: convert struct device of_node to fwnode usage Lorenzo Pieralisi
2016-11-09 14:43 ` Robin Murphy
2016-11-09 14:19 ` [PATCH v7 06/16] drivers: iommu: arm-smmu-v3: " Lorenzo Pieralisi
2016-11-09 14:44 ` Robin Murphy
2016-11-09 14:19 ` [PATCH v7 07/16] drivers: acpi: implement acpi_dma_configure Lorenzo Pieralisi
2016-11-09 15:33 ` Robin Murphy
2016-11-16 0:55 ` Rafael J. Wysocki
2016-11-09 14:19 ` [PATCH v7 08/16] drivers: acpi: iort: add node match function Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 09/16] drivers: acpi: iort: add support for ARM SMMU platform devices creation Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 10/16] drivers: iommu: arm-smmu-v3: split probe functions into DT/generic portions Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 11/16] drivers: iommu: arm-smmu-v3: add IORT configuration Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 12/16] drivers: iommu: arm-smmu: split probe functions into DT/generic portions Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 13/16] drivers: iommu: arm-smmu: add IORT configuration Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 14/16] drivers: acpi: iort: replace rid map type with type mask Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 15/16] drivers: acpi: iort: add single mapping function Lorenzo Pieralisi
2016-11-09 14:19 ` [PATCH v7 16/16] drivers: acpi: iort: introduce iort_iommu_configure Lorenzo Pieralisi
2016-11-16 0:56 ` Rafael J. Wysocki
2016-11-09 23:36 ` [PATCH v7 00/16] ACPI IORT ARM SMMU support Rafael J. Wysocki
2016-11-10 10:58 ` Lorenzo Pieralisi
2016-11-15 10:12 ` Lorenzo Pieralisi
2016-11-15 13:04 ` Rafael J. Wysocki
2016-11-15 14:07 ` Lorenzo Pieralisi
2016-11-11 12:44 ` Hanjun Guo
2016-11-16 13:28 ` Tomasz Nowicki
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=20161114102654.GA1677@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=linux-arm-kernel@lists.infradead.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: 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 NNTP newsgroup(s).