Am 29.09.2014 20:55, schrieb Andy Lutomirski: > On Wed, Sep 17, 2014 at 7:16 AM, Michael S. Tsirkin <mst@xxxxxxxxxx> wrote: >> On Wed, Sep 17, 2014 at 08:02:31AM -0400, Benjamin Herrenschmidt wrote: >>> On Tue, 2014-09-16 at 22:22 -0700, Andy Lutomirski wrote: >>>> On non-PPC systems, virtio_pci should use the DMA API. This fixes >>>> virtio_pci on Xen. On PPC, using the DMA API would break things, so >>>> we need to preserve the old behavior. >>>> >>>> The big comment in this patch explains the considerations in more >>>> detail. >>> >>> I still disagree with using CONFIG_PPC as a trigger here. >>> >>> Fundamentally, the qemu implementation today bypasses IOMMUs on all >>> platforms as far as I can tell. >>> >>> If that changes, we'll have a backward compatibility problem. >>> >>> The virtio device should advertise whether it's using that bypass >>> mode of operation and virtio_pci should react accordingly. >> >> Well if there's a way to detect that - that's outside the >> device, then we probably shouldn't use device-specific >> interfaces for this capability. >> >> >>> There is a demand for being able to operate on top of an IOMMU on >>> powerpc as well for some embedded stuff using PCI as a transport so your >>> patch precludes that. >>> >>> Cheers, >>> Ben. >> >> As far as I can see, nothing changes on PPC so this patch >> does not preclude anything that was working? > > Rusty and Michael, what's the status of this? > > I think that (aside from the trivial DMI/DMA typo) the only real issue > here is that the situation on PPC is ugly. We're failing to enable > physical virtio hardware on PPC with these patches, but that never > worked anyway. I don't think that there are any regressions other > than ugliness. > > My preference would be to apply the patches as is (or with "DMA" > spelled correctly), and then to: > > - Make sure that all virtio-mmio systems have working DMA ops so that > virtio-mmio can the DMA API > > - Fix the DMA API on s390 (probably easy) and on PPC (not necessarily so easy) Just as a comment: On s390 we always considered the memory access as access to real memory (not device memory) for virtio accesses. I prefer to not touch the DMA API on s390 as it is quite s390-PCI specific but it is somewhat strange for CCW devices. We would basically have two kinds of DMA mappings on s390 then, one iommu like for the PCI devices and one that maps DMA memory 1:1 to real memory. We would also need some buy-in from the s390 arch maintainers then. > > - Remove the non-DMA-API code, which would be a very small change on > top of these patches. > > --Andy > -- > To unsubscribe from this list: send the line "unsubscribe linux-s390" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization
