summaryrefslogtreecommitdiff
path: root/include/xen
diff options
context:
space:
mode:
authorOleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>2022-06-02 22:23:50 +0300
committerJuergen Gross <jgross@suse.com>2022-06-06 17:07:30 +0300
commitadd413a1d966d8458571a2571881903d234a9f8e (patch)
tree14f23c0c6a25e4aa1074fa8e698da92dac25d674 /include/xen
parentfa1f57421e0b1c57843902c89728f823abc32f02 (diff)
downloadlinux-add413a1d966d8458571a2571881903d234a9f8e.tar.xz
dt-bindings: Add xen,grant-dma IOMMU description for xen-grant DMA ops
The main purpose of this binding is to communicate Xen specific information using generic IOMMU device tree bindings (which is a good fit here) rather than introducing a custom property. Introduce Xen specific IOMMU for the virtualized device (e.g. virtio) to be used by Xen grant DMA-mapping layer in the subsequent commit. The reference to Xen specific IOMMU node using "iommus" property indicates that Xen grant mappings need to be enabled for the device, and it specifies the ID of the domain where the corresponding backend resides. The domid (domain ID) is used as an argument to the Xen grant mapping APIs. This is needed for the option to restrict memory access using Xen grant mappings to work which primary goal is to enable using virtio devices in Xen guests. Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> Reviewed-by: Stefano Stabellini <sstabellini@kernel.org> Reviewed-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/1654197833-25362-6-git-send-email-olekstysh@gmail.com Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'include/xen')
0 files changed, 0 insertions, 0 deletions