On Tue, Aug 7, 2012 at 3:52 PM, Cornelia Huck <cornelia.huck@xxxxxxxxxx> wrote: > Add a new virtio transport that uses channel commands to perform > virtio operations. > > Add a new machine type s390-ccw that uses this virtio-ccw transport > and make it the default machine for s390. > > Signed-off-by: Cornelia Huck <cornelia.huck@xxxxxxxxxx> > --- > hw/qdev-monitor.c | 5 + > hw/s390-virtio.c | 268 ++++++++++---- > hw/s390x/Makefile.objs | 1 + > hw/s390x/virtio-ccw.c | 962 +++++++++++++++++++++++++++++++++++++++++++++++++ > hw/s390x/virtio-ccw.h | 77 ++++ > vl.c | 1 + > 6 files changed, 1243 insertions(+), 71 deletions(-) > create mode 100644 hw/s390x/virtio-ccw.c > create mode 100644 hw/s390x/virtio-ccw.h Is the virtqueue still using vring and assuming the hypervisor reaches into guest memory? Can existing ccw device types access memory directly (for some reason I assumed ccw always copies or send messages)? Stefan -- 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
