search for: misdescrib

...turn false; > +} > + I'd quite like to see this be an explicit opt-out for the known-broken platforms. We've listed the SPARC and PPC64 issues. For x86 I need to refresh my memory as a prelude to trying to fix it... was the issue *just* that Qemu tends to ship with a broken BIOS that misdescribes the virtio devices (and any assigned PCI devices) as being behind an IOMMU when they're not, in the rare case that Qemu actually exposes its partially-implemented virtual IOMMU to the guest? Could we have an arch_vring_eschew_dma_api(dev) function which the affected architectures could provi...

...turn false; > +} > + I'd quite like to see this be an explicit opt-out for the known-broken platforms. We've listed the SPARC and PPC64 issues. For x86 I need to refresh my memory as a prelude to trying to fix it... was the issue *just* that Qemu tends to ship with a broken BIOS that misdescribes the virtio devices (and any assigned PCI devices) as being behind an IOMMU when they're not, in the rare case that Qemu actually exposes its partially-implemented virtual IOMMU to the guest? Could we have an arch_vring_eschew_dma_api(dev) function which the affected architectures could provi...

...+ > > I'd quite like to see this be an explicit opt-out for the known-broken > platforms. We've listed the SPARC and PPC64 issues. For x86 I need to > refresh my memory as a prelude to trying to fix it... was the issue > *just* that Qemu tends to ship with a broken BIOS that misdescribes the > virtio devices (and any assigned PCI devices) as being behind an IOMMU > when they're not, in the rare case that Qemu actually exposes its > partially-implemented virtual IOMMU to the guest? > > Could we have an arch_vring_eschew_dma_api(dev) function which the > affe...

...I'd quite like to see this be an explicit opt-out for the known-broken >> platforms. We've listed the SPARC and PPC64 issues. For x86 I need to >> refresh my memory as a prelude to trying to fix it... was the issue >> *just* that Qemu tends to ship with a broken BIOS that misdescribes the >> virtio devices (and any assigned PCI devices) as being behind an IOMMU >> when they're not, in the rare case that Qemu actually exposes its >> partially-implemented virtual IOMMU to the guest? >> >> Could we have an arch_vring_eschew_dma_api(dev) function...

...I'd quite like to see this be an explicit opt-out for the known-broken >> platforms. We've listed the SPARC and PPC64 issues. For x86 I need to >> refresh my memory as a prelude to trying to fix it... was the issue >> *just* that Qemu tends to ship with a broken BIOS that misdescribes the >> virtio devices (and any assigned PCI devices) as being behind an IOMMU >> when they're not, in the rare case that Qemu actually exposes its >> partially-implemented virtual IOMMU to the guest? >> >> Could we have an arch_vring_eschew_dma_api(dev) function...

This switches virtio to use the DMA API on Xen and if requested by module option. This fixes virtio on Xen, and it should break anything because it's off by default on everything except Xen PV on x86. To the Xen people: is this okay? If it doesn't work on other Xen variants (PVH? HVM?), can you submit follow-up patches to fix it? To everyone else: we've waffled on this for way too

This switches virtio to use the DMA API on Xen and if requested by module option. This fixes virtio on Xen, and it should break anything because it's off by default on everything except Xen PV on x86. To the Xen people: is this okay? If it doesn't work on other Xen variants (PVH? HVM?), can you submit follow-up patches to fix it? To everyone else: we've waffled on this for way too