From c01a259dbbd36e53bf6a34e5f7814a9fbd99b44e Mon Sep 17 00:00:00 2001 From: "cornelia.huck" Date: Mon, 4 Nov 2013 14:32:55 +0000 Subject: ccw: Remove reference to old s390-virtio transport. Historical notes for a mechanism that was never officially specced do not add anything to the standard. Signed-off-by: Cornelia Huck git-svn-id: https://tools.oasis-open.org/version-control/svn/virtio@83 0c8fb4dd-22a2-4bb5-bc14-6c75a5f43652 --- virtio-v1.0-wd01-part1-specification.txt | 7 ------- 1 file changed, 7 deletions(-) diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt index c9f3cf3..18cb6b6 100644 --- a/virtio-v1.0-wd01-part1-specification.txt +++ b/virtio-v1.0-wd01-part1-specification.txt @@ -1703,13 +1703,6 @@ Notification mechanisms did not change. S/390 based virtual machines support neither PCI nor MMIO, so a different transport is needed there. -The old s390-virtio mechanism used a special page mapped above -the guest's memory and several diagnose calls (hypercalls); it -does have some drawbacks, however, like a rather limited number -of devices and very restricted hotplug support. Moreover, device -discovery and operation differ from other environments on the -S/390 platform. - virtio-ccw uses the standard channel I/O based mechanism used for the majority of devices on S/390. A virtual channel device with a special control unit type acts as proxy to the virtio device -- cgit v1.2.3