diff options
author | Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> | 2022-06-02 21:23:52 +0200 |
---|---|---|
committer | Juergen Gross <jgross@suse.com> | 2022-06-06 16:07:30 +0200 |
commit | 625ab90ecdf7770bda7ae21c4d5c938aa9b43bb4 (patch) | |
tree | 6992c0524fa71479bdc60df7cdd6080f5e270621 /drivers/xen/Kconfig | |
parent | xen/grant-dma-iommu: Introduce stub IOMMU driver (diff) | |
download | linux-625ab90ecdf7770bda7ae21c4d5c938aa9b43bb4.tar.xz linux-625ab90ecdf7770bda7ae21c4d5c938aa9b43bb4.zip |
xen/grant-dma-ops: Retrieve the ID of backend's domain for DT devices
Use the presence of "iommus" property pointed to the IOMMU node with
recently introduced "xen,grant-dma" compatible as a clear indicator
of enabling Xen grant mappings scheme for that device and read the ID
of Xen domain where the corresponding backend is running. The domid
(domain ID) is used as an argument to the Xen grant mapping APIs.
To avoid the deferred probe timeout which takes place after reusing
generic IOMMU device tree bindings (because the IOMMU device never
becomes available) enable recently introduced stub IOMMU driver by
selecting XEN_GRANT_DMA_IOMMU.
Also introduce xen_is_grant_dma_device() to check whether xen-grant
DMA ops need to be set for a passed device.
Remove the hardcoded domid 0 in xen_grant_setup_dma_ops().
Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Link: https://lore.kernel.org/r/1654197833-25362-8-git-send-email-olekstysh@gmail.com
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'drivers/xen/Kconfig')
-rw-r--r-- | drivers/xen/Kconfig | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index 35d20d90390b..bfd5f4f706bc 100644 --- a/drivers/xen/Kconfig +++ b/drivers/xen/Kconfig @@ -347,6 +347,7 @@ config XEN_VIRTIO bool "Xen virtio support" depends on VIRTIO select XEN_GRANT_DMA_OPS + select XEN_GRANT_DMA_IOMMU if OF help Enable virtio support for running as Xen guest. Depending on the guest type this will require special support on the backend side |