Displaying 7 results from an estimated 7 matches for "virtio_ring_xen".
2015 Jul 28
4
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...s: I think that QEMU now supports a nasty
mode in which the guest's PCI bus appears to be behind an IOMMU but
the virtio devices on that bus punch straight through that IOMMU.
I have a half-hearted port to modern kernels here:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=virtio_ring_xen
I didn't implement DMA API access for virtio_pci_modern, and I have no
idea what to do about detecting whether a given virtio device honors
its IOMMU or not.
--Andy
2015 Jul 28
4
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...s: I think that QEMU now supports a nasty
mode in which the guest's PCI bus appears to be behind an IOMMU but
the virtio devices on that bus punch straight through that IOMMU.
I have a half-hearted port to modern kernels here:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=virtio_ring_xen
I didn't implement DMA API access for virtio_pci_modern, and I have no
idea what to do about detecting whether a given virtio device honors
its IOMMU or not.
--Andy
2015 Jul 28
0
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...hange.
The plan was:
- for PPC, virtio never honors IOMMU
- for non-PPC, either have virtio always honor IOMMU, or enforce that
virtio is not under IOMMU.
Paolo
> I have a half-hearted port to modern kernels here:
>
> https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=virtio_ring_xen
>
> I didn't implement DMA API access for virtio_pci_modern, and I have no
> idea what to do about detecting whether a given virtio device honors
> its IOMMU or not.
>
> --Andy
>
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...properly
reflect the fact that in qemu you can mix & match IOMMU-honoring devices
and bypassing-virtio on the same bus).
Ben.
> Paolo
>
> > I have a half-hearted port to modern kernels here:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=virtio_ring_xen
> >
> > I didn't implement DMA API access for virtio_pci_modern, and I have no
> > idea what to do about detecting whether a given virtio device honors
> > its IOMMU or not.
> >
> > --Andy
> >
2015 Jul 28
2
[PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
...properly
reflect the fact that in qemu you can mix & match IOMMU-honoring devices
and bypassing-virtio on the same bus).
Ben.
> Paolo
>
> > I have a half-hearted port to modern kernels here:
> >
> > https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=virtio_ring_xen
> >
> > I didn't implement DMA API access for virtio_pci_modern, and I have no
> > idea what to do about detecting whether a given virtio device honors
> > its IOMMU or not.
> >
> > --Andy
> >
2014 Aug 25
6
virtio DMA API?
Currently, a lot of the virtio code assumes that bus (i.e. hypervisor)
addresses are the same as physical address. This is false on Xen, so
virtio is completely broken. I wouldn't be surprised if it also
becomes a problem the first time that someone sticks a physical
"virtio" device on a 32-bit bus on an ARM SOC with more than 4G RAM.
Would you accept patches to convert
2014 Aug 25
6
virtio DMA API?
Currently, a lot of the virtio code assumes that bus (i.e. hypervisor)
addresses are the same as physical address. This is false on Xen, so
virtio is completely broken. I wouldn't be surprised if it also
becomes a problem the first time that someone sticks a physical
"virtio" device on a 32-bit bus on an ARM SOC with more than 4G RAM.
Would you accept patches to convert