Displaying 5 results from an estimated 5 matches for "topo_offset".
2019 Nov 22
0
[RFC virtio 12/13] virtio-iommu: Add built-in topology description
...iommu.tex
+++ b/virtio-iommu.tex
@@ -67,6 +67,9 @@ \subsection{Feature bits}\label{sec:Device Types / IOMMU Device / Feature bits}
\item[VIRTIO_IOMMU_F_MMIO (5)]
The VIRTIO_IOMMU_MAP_F_MMIO flag is available.
+
+\item[VIRTIO_IOMMU_F_TOPOLOGY (6)]
+ Topology description is available at \field{topo_offset}.
\end{description}
\drivernormative{\subsubsection}{Feature bits}{Device Types / IOMMU Device / Feature bits}
@@ -97,6 +100,7 @@ \subsection{Device configuration layout}\label{sec:Device Types / IOMMU Device /
le32 end;
} domain_range;
le32 probe_size;
+ le16 topo_offset;
};
\end...
2019 Nov 22
1
[RFC 13/13] iommu/virtio: Add topology description to
...*dev_cfg)
> +{
> + u32 offset;
> + struct viommu_topology cap;
> + struct viommu_spec *viommu_spec;
> + int iter = 0; /* Protects against config loop */
> +
> + offset = viommu_cread(dev, pci_cfg, dev_cfg, 2,
> + offsetof(struct virtio_iommu_config,
> + topo_offset));
> + if (!offset)
> + return 0;
> +
> + viommu_spec = kzalloc(sizeof(*viommu_spec), GFP_KERNEL);
> + if (!viommu_spec)
> + return -ENOMEM;
> +
> + INIT_LIST_HEAD(&viommu_spec->topology);
> + viommu_spec->dev = &dev->dev;
> +
> + while (offset &g...
2019 Nov 22
0
[RFC 13/13] iommu/virtio: Add topology description to
..., int pci_cfg,
+ struct viommu_cap_config *dev_cfg)
+{
+ u32 offset;
+ struct viommu_topology cap;
+ struct viommu_spec *viommu_spec;
+ int iter = 0; /* Protects against config loop */
+
+ offset = viommu_cread(dev, pci_cfg, dev_cfg, 2,
+ offsetof(struct virtio_iommu_config,
+ topo_offset));
+ if (!offset)
+ return 0;
+
+ viommu_spec = kzalloc(sizeof(*viommu_spec), GFP_KERNEL);
+ if (!viommu_spec)
+ return -ENOMEM;
+
+ INIT_LIST_HEAD(&viommu_spec->topology);
+ viommu_spec->dev = &dev->dev;
+
+ while (offset >= sizeof(struct virtio_iommu_config) && ++ite...
2019 Nov 22
16
[RFC 00/13] virtio-iommu on non-devicetree platforms
I'm seeking feedback on multi-platform support for virtio-iommu. At the
moment only devicetree (DT) is supported and we don't have a pleasant
solution for other platforms. Once we figure out the topology
description, x86 support is trivial.
Since the IOMMU manages memory accesses from other devices, the guest
kernel needs to initialize the IOMMU before endpoints start issuing DMA.
2019 Nov 22
16
[RFC 00/13] virtio-iommu on non-devicetree platforms
I'm seeking feedback on multi-platform support for virtio-iommu. At the
moment only devicetree (DT) is supported and we don't have a pleasant
solution for other platforms. Once we figure out the topology
description, x86 support is trivial.
Since the IOMMU manages memory accesses from other devices, the guest
kernel needs to initialize the IOMMU before endpoints start issuing DMA.