From: Jean-Philippe Brucker <jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> To: "Michael S. Tsirkin" <mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>, Jean-philippe Brucker <jphilippe.brucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Cc: mark.rutland-5wv7dgnIgG8@public.gmane.org, devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, kevin.tian-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org, tnowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org, peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org, marc.zyngier-5wv7dgnIgG8@public.gmane.org, linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, jasowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org, will.deacon-5wv7dgnIgG8@public.gmane.org, virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Bjorn Helgaas <helgaas-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>, robin.murphy-5wv7dgnIgG8@public.gmane.org, kvmarm-FPEHb7Xf0XXUo1n7N8X6UoWGPAHP3yOg@public.gmane.org Subject: Re: [PATCH v3 3/7] PCI: OF: Allow endpoints to bypass the iommu Date: Mon, 22 Oct 2018 12:27:50 +0100 [thread overview] Message-ID: <e5c44d21-7b43-32dd-4f5f-3136bacb07e0@arm.com> (raw) In-Reply-To: <20181017111100-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> On 17/10/2018 16:14, Michael S. Tsirkin wrote: >>> Thinking about this comment, I would like to ask: can't the >>> virtio device indicate the ranges in a portable way? >>> This would minimize the dependency on dt bindings and ACPI, >>> enabling support for systems that have neither but do >>> have virtio e.g. through pci. >> >> I thought about adding a PROBE request for this in virtio-iommu, but it >> wouldn't be usable by a Linux guest because of a bootstrapping problem. > > Hmm. At some level it seems wrong to design hardware interfaces > around how Linux happens to probe things. That can change at any time > ... I suspect that most other OS will also solve this class of problem using a standard such as DT or ACPI, because they also provide dependency for clock, interrupts, power management, etc. We can add a self-contained PROBE method if someone makes a case for it, but it's unlikely to get used at all, and nearly impossible to implement in Linux. The host would still need a method to tell the guest which device to probe first, for example with kernel parameters. >> Early on, Linux needs a description of device dependencies, to determine >> in which order to probe them. If the device dependency was described by >> virtio-iommu itself, the guest could for example initialize a NIC, >> allocate buffers and start DMA on the physical address space (which aborts >> if the IOMMU implementation disallows DMA by default), only to find out >> once the virtio-iommu module is loaded that it needs to cancel all DMA and >> reconfigure the NIC. With a static description such as iommu-map in DT or >> ACPI remapping tables, the guest can defer probing of the NIC until the >> IOMMU is initialized. >> >> Thanks, >> Jean > > Could you point me at the code you refer to here? In drivers/base/dd.c, really_probe() calls dma_configure() before the device driver's probe(). dma_configure() ends up calling either of_dma_configure() or acpi_dma_configure(), which return -EPROBE_DEFER if the device's IOMMU isn't yet available. In that case the device is added to the deferred pending list. After another device is successfully bound to a driver, all devices on the pending list are retried (driver_deferred_probe_trigger()), and if the dependency has been resolved, then dma_configure() succeeds. Another method (used by Intel and AMD IOMMU drivers) is to initialize the IOMMU as early as possible, after discovering it in the ACPI tables and before probing other devices. This can't work for virtio-iommu because the driver might be a module, in which case early init isn't possible. We have to defer probe of all dependent devices until the virtio and virtio-iommu modules are loaded. Thanks, Jean
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com> To: "Michael S. Tsirkin" <mst@redhat.com>, Jean-philippe Brucker <jphilippe.brucker@gmail.com> Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, kevin.tian@intel.com, tnowicki@caviumnetworks.com, peter.maydell@linaro.org, marc.zyngier@arm.com, linux-pci@vger.kernel.org, jasowang@redhat.com, will.deacon@arm.com, virtualization@lists.linux-foundation.org, iommu@lists.linux-foundation.org, robh+dt@kernel.org, Bjorn Helgaas <helgaas@kernel.org>, robin.murphy@arm.com, kvmarm@lists.cs.columbia.edu Subject: Re: [PATCH v3 3/7] PCI: OF: Allow endpoints to bypass the iommu Date: Mon, 22 Oct 2018 12:27:50 +0100 [thread overview] Message-ID: <e5c44d21-7b43-32dd-4f5f-3136bacb07e0@arm.com> (raw) In-Reply-To: <20181017111100-mutt-send-email-mst@kernel.org> On 17/10/2018 16:14, Michael S. Tsirkin wrote: >>> Thinking about this comment, I would like to ask: can't the >>> virtio device indicate the ranges in a portable way? >>> This would minimize the dependency on dt bindings and ACPI, >>> enabling support for systems that have neither but do >>> have virtio e.g. through pci. >> >> I thought about adding a PROBE request for this in virtio-iommu, but it >> wouldn't be usable by a Linux guest because of a bootstrapping problem. > > Hmm. At some level it seems wrong to design hardware interfaces > around how Linux happens to probe things. That can change at any time > ... I suspect that most other OS will also solve this class of problem using a standard such as DT or ACPI, because they also provide dependency for clock, interrupts, power management, etc. We can add a self-contained PROBE method if someone makes a case for it, but it's unlikely to get used at all, and nearly impossible to implement in Linux. The host would still need a method to tell the guest which device to probe first, for example with kernel parameters. >> Early on, Linux needs a description of device dependencies, to determine >> in which order to probe them. If the device dependency was described by >> virtio-iommu itself, the guest could for example initialize a NIC, >> allocate buffers and start DMA on the physical address space (which aborts >> if the IOMMU implementation disallows DMA by default), only to find out >> once the virtio-iommu module is loaded that it needs to cancel all DMA and >> reconfigure the NIC. With a static description such as iommu-map in DT or >> ACPI remapping tables, the guest can defer probing of the NIC until the >> IOMMU is initialized. >> >> Thanks, >> Jean > > Could you point me at the code you refer to here? In drivers/base/dd.c, really_probe() calls dma_configure() before the device driver's probe(). dma_configure() ends up calling either of_dma_configure() or acpi_dma_configure(), which return -EPROBE_DEFER if the device's IOMMU isn't yet available. In that case the device is added to the deferred pending list. After another device is successfully bound to a driver, all devices on the pending list are retried (driver_deferred_probe_trigger()), and if the dependency has been resolved, then dma_configure() succeeds. Another method (used by Intel and AMD IOMMU drivers) is to initialize the IOMMU as early as possible, after discovering it in the ACPI tables and before probing other devices. This can't work for virtio-iommu because the driver might be a module, in which case early init isn't possible. We have to defer probe of all dependent devices until the virtio and virtio-iommu modules are loaded. Thanks, Jean
next prev parent reply other threads:[~2018-10-22 11:27 UTC|newest] Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-12 14:59 [PATCH v3 0/7] Add virtio-iommu driver Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` [PATCH v3 1/7] dt-bindings: virtio-mmio: Add IOMMU description Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-18 0:30 ` Rob Herring [not found] ` <20181012145917.6840-2-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> 2018-10-18 0:30 ` Rob Herring 2018-10-18 0:30 ` Rob Herring 2018-11-15 8:45 ` Auger Eric 2018-11-15 8:45 ` Auger Eric 2018-10-12 14:59 ` [PATCH v3 2/7] dt-bindings: virtio: Add virtio-pci-iommu node Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-18 0:35 ` Rob Herring 2018-10-18 0:35 ` Rob Herring 2018-10-18 0:35 ` Rob Herring 2018-11-15 8:45 ` Auger Eric 2018-11-15 8:45 ` Auger Eric 2018-11-15 8:45 ` Auger Eric 2018-10-12 14:59 ` [PATCH v3 3/7] PCI: OF: Allow endpoints to bypass the iommu Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker [not found] ` <20181012145917.6840-4-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> 2018-10-12 19:41 ` Bjorn Helgaas 2018-10-12 19:41 ` Bjorn Helgaas 2018-10-15 10:52 ` Michael S. Tsirkin 2018-10-15 11:32 ` Robin Murphy [not found] ` <20181012194158.GX5906-1RhO1Y9PlrlHTL0Zs8A6p5iNqAH0jzoTYJqu5kTmcBRl57MIdRCFDg@public.gmane.org> 2018-10-15 10:52 ` Michael S. Tsirkin 2018-10-15 10:52 ` Michael S. Tsirkin [not found] ` <20181015065024-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2018-10-15 19:46 ` Jean-philippe Brucker 2018-10-15 19:46 ` Jean-philippe Brucker 2018-10-17 15:14 ` Michael S. Tsirkin 2018-10-17 15:14 ` Michael S. Tsirkin 2018-10-18 10:47 ` Robin Murphy 2018-10-18 10:47 ` Robin Murphy 2018-10-18 10:47 ` Robin Murphy [not found] ` <20181017111100-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2018-10-22 11:27 ` Jean-Philippe Brucker [this message] 2018-10-22 11:27 ` Jean-Philippe Brucker 2018-10-22 11:27 ` Jean-Philippe Brucker 2018-10-15 11:32 ` Robin Murphy 2018-10-15 11:32 ` Robin Murphy 2018-10-15 19:45 ` Jean-philippe Brucker 2018-10-15 19:45 ` Jean-philippe Brucker 2018-10-12 14:59 ` [PATCH v3 4/7] PCI: OF: Initialize dev->fwnode appropriately Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker [not found] ` <20181012145917.6840-5-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> 2018-10-12 19:44 ` Bjorn Helgaas 2018-10-12 19:44 ` Bjorn Helgaas 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` [PATCH v3 5/7] iommu: Add virtio-iommu driver Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 16:35 ` Michael S. Tsirkin 2018-10-12 16:35 ` Michael S. Tsirkin 2018-10-12 16:35 ` Michael S. Tsirkin [not found] ` <20181012120953-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2018-10-12 18:54 ` Jean-Philippe Brucker 2018-10-12 18:54 ` Jean-Philippe Brucker 2018-10-12 18:54 ` Jean-Philippe Brucker 2018-11-08 14:51 ` Auger Eric 2018-11-08 14:51 ` Auger Eric 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-08 14:51 ` Auger Eric 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` [PATCH v3 6/7] iommu/virtio: Add probe request Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 16:42 ` Michael S. Tsirkin 2018-10-12 16:42 ` Michael S. Tsirkin 2018-11-08 14:48 ` Auger Eric [not found] ` <20181012145917.6840-7-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> 2018-11-08 14:48 ` Auger Eric 2018-11-08 14:48 ` Auger Eric [not found] ` <295d30bb-5aef-2727-01c0-ec10c7a8fa8c-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-08 16:46 ` Jean-Philippe Brucker 2018-11-15 13:20 ` Auger Eric 2018-11-15 13:20 ` Auger Eric 2018-11-15 16:22 ` Jean-Philippe Brucker 2018-11-15 16:22 ` Jean-Philippe Brucker 2018-11-15 16:22 ` Jean-Philippe Brucker 2018-11-15 13:20 ` Auger Eric 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` [PATCH v3 7/7] iommu/virtio: Add event queue Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 14:59 ` Jean-Philippe Brucker 2018-10-12 17:00 ` [PATCH v3 0/7] Add virtio-iommu driver Michael S. Tsirkin [not found] ` <20181012145917.6840-1-jean-philippe.brucker-5wv7dgnIgG8@public.gmane.org> 2018-10-12 17:00 ` Michael S. Tsirkin 2018-10-12 17:00 ` Michael S. Tsirkin 2018-10-12 18:55 ` Jean-Philippe Brucker [not found] ` <20181012125443-mutt-send-email-mst-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> 2018-10-12 18:55 ` Jean-Philippe Brucker 2018-10-12 18:55 ` Jean-Philippe Brucker 2018-10-16 9:25 ` Auger Eric 2018-10-16 9:25 ` Auger Eric 2018-10-16 18:44 ` Jean-Philippe Brucker 2018-10-16 18:44 ` Jean-Philippe Brucker 2018-10-16 20:31 ` Auger Eric 2018-10-16 20:31 ` Auger Eric 2018-10-17 11:54 ` Jean-Philippe Brucker 2018-10-17 11:54 ` Jean-Philippe Brucker 2018-10-17 15:23 ` Michael S. Tsirkin 2018-10-17 15:23 ` Michael S. Tsirkin 2018-10-17 15:23 ` Michael S. Tsirkin 2018-10-16 18:44 ` Jean-Philippe Brucker 2018-10-16 9:25 ` Auger Eric
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=e5c44d21-7b43-32dd-4f5f-3136bacb07e0@arm.com \ --to=jean-philippe.brucker-5wv7dgnigg8@public.gmane.org \ --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=helgaas-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \ --cc=jasowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \ --cc=jphilippe.brucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \ --cc=kevin.tian-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \ --cc=kvmarm-FPEHb7Xf0XXUo1n7N8X6UoWGPAHP3yOg@public.gmane.org \ --cc=linux-pci-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=marc.zyngier-5wv7dgnIgG8@public.gmane.org \ --cc=mark.rutland-5wv7dgnIgG8@public.gmane.org \ --cc=mst-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \ --cc=peter.maydell-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \ --cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \ --cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \ --cc=tnowicki-M3mlKVOIwJVv6pq1l3V1OdBPR1lH4CV8@public.gmane.org \ --cc=virtualization-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.