Am 29.10.2015 um 07:22 schrieb Andy Lutomirski: > On Tue, Oct 27, 2015 at 3:48 PM, Christian Borntraeger > <borntraeger@xxxxxxxxxx> wrote: >> This is an RFC to check if I am on the right track. There >> are some attempts to unify the dma ops (Christoph) as well >> as some attempts to make virtio use the dma API (Andy). >> >> At todays discussion at the kernel summit, we concluded that >> we want to use the same code on all platforms, whereever >> possible, so having a dummy dma_op might be the easiest >> solution to keep virtio-ccw as similar as possible to >> virtio-pci. Andy Lutomirski will rework his patchset to >> unconditionally use the dma ops. We will also need a >> compatibility quirk for powerpc to bypass the iommu mappings >> on older QEMU version (which translates to all versions as >> of today) and per device, e.g. via device tree. Ben >> Herrenschmidt will look into that. > > The combination of these patches plus my series don't link for me > unless I enable PCI. Would s390 need to select HAS_DMA from VIRTIO or > something similar? Well, actually this is a potential improvement for series. I could just make the noop dma ops default for _all_ devices unless it has a per device dma_ops (e.g. s390 pci) and the unconditionally set HAS_DMA. > > Also, is it possible to use QEMU to emulate an s390x? Even just: > > qemu-system-s390x -M s390-ccw-virtio Yes, we have no interactive bios and if no boot device is there is bios will load a disabled wait, which will exit qemu. Make sure to compile your kernel for z900 (processor type) as qemu does not handle all things of newer processors. You can then do qemu-system-s390x -nographic -m 256 -kernel vmlinux -initrd <something> -- 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
