similar to: [PATCH] virtio-spec: document indirect descriptors

Hi Rusty, here is the specification for a virtio-based SCSI host (controller, HBA, you name it) so that you can apply it to the spec document and publish it. I changed the index from 7 to 8 to account for the rpmsg device, and added a feature bit to tell the guest in advance whether the host supports hotplug. Otherwise there is no change from v2. Paolo --- virtio-spec.lyx.saved 2011-11-29

Hi Rusty, here is the specification for a virtio-based SCSI host (controller, HBA, you name it) so that you can apply it to the spec document and publish it. I changed the index from 7 to 8 to account for the rpmsg device, and added a feature bit to tell the guest in advance whether the host supports hotplug. Otherwise there is no change from v2. Paolo --- virtio-spec.lyx.saved 2011-11-29

Add an rpmsg appendix to the virtio spec and tag it as Appendix H. Push the SCSI host appendix to 'I' so the appendices order stays according to the virtio device ids. Patch is against: http://ozlabs.org/~rusty/virtio-spec/virtio-0.9.4.lyx Tested with LyX 2.0.0. Signed-off-by: Ohad Ben-Cohen <ohad at wizery.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc:

Add an rpmsg appendix to the virtio spec and tag it as Appendix H. Push the SCSI host appendix to 'I' so the appendices order stays according to the virtio device ids. Patch is against: http://ozlabs.org/~rusty/virtio-spec/virtio-0.9.4.lyx Tested with LyX 2.0.0. Signed-off-by: Ohad Ben-Cohen <ohad at wizery.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc:

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

Hi all, here is the specification for a virtio-based SCSI host (controller, HBA, you name it). The virtio SCSI host is the basis of an alternative storage stack for KVM. This stack would overcome several limitations of the current solution, virtio-blk: 1) scalability limitations: virtio-blk-over-PCI puts a strong upper limit on the number of devices that can be added to a guest. Common

The diff below is an update to virtio-spec with specification of a stats vq added to virtio-blk. The idea behind adding a stats vq is to simplify pull of information which exists only on the guest and can't be collected on the host. The idea is basically same as the stats vq which exists in virtio-balloon and reporting host memory statistics. --- diff --git a/old/virtio-spec.lyx

The diff below is an update to virtio-spec with specification of a stats vq added to virtio-blk. The idea behind adding a stats vq is to simplify pull of information which exists only on the guest and can't be collected on the host. The idea is basically same as the stats vq which exists in virtio-balloon and reporting host memory statistics. --- diff --git a/old/virtio-spec.lyx

I'm working on a patchset (to follow shortly) that modified the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Especially for testing, it is very convenient to have separate feature bits

I'm working on a patchset (to follow shortly) that modified the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Especially for testing, it is very convenient to have separate feature bits

Add an option to modify the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Since we've run out of bits in the 32 bit field, I added another 32 bit and bit 31 enables that. I started with

Add an option to modify the notificatin hand-off in virtio to be basically like Xen: each side published an index, the other side only triggers an event when it crosses that index value (Xen event indexes start at 1, ours start at 0 for backward-compatiblity, but that's minor). Since we've run out of bits in the 32 bit field, I added another 32 bit and bit 31 enables that. I started with

Add basic documentation for virtio-9p. I can expand more on device operation, but I don't think there's anything significant enough for the spec to be mentioned there. Please let me know if I'm wrong. Signed-off-by: Sasha Levin <sasha.levin at oracle.com> --- virtio-spec.lyx | 206 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 206 insertions(+) diff

Add basic documentation for virtio-9p. I can expand more on device operation, but I don't think there's anything significant enough for the spec to be mentioned there. Please let me know if I'm wrong. Signed-off-by: Sasha Levin <sasha.levin at oracle.com> --- virtio-spec.lyx | 206 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 206 insertions(+) diff

The virtio-console device has recently been updated to support multiple devices and multiple ports. These ports can also function as generic serial ports. Reflect these changes in the spec. Signed-off-by: Amit Shah <amit.shah at redhat.com> --- virtio-spec/virtio-spec-0.8.3.lyx.orig 2010-01-20 19:21:02.239131766 +0530 +++ virtio-spec/virtio-spec-0.8.3.lyx 2010-01-20 19:21:02.228131971

The virtio-console device has recently been updated to support multiple devices and multiple ports. These ports can also function as generic serial ports. Reflect these changes in the spec. Signed-off-by: Amit Shah <amit.shah at redhat.com> --- virtio-spec/virtio-spec-0.8.3.lyx.orig 2010-01-20 19:21:02.239131766 +0530 +++ virtio-spec/virtio-spec-0.8.3.lyx 2010-01-20 19:21:02.228131971

I took a stub at documenting CMD and FLUSH request types in virtio block. Christoph, could you look over this please? I note that the interface seems full of warts to me, this might be a first step to cleaning them. One issue I struggled with especially is how type field mixes bits and non-bit values. I ended up simply defining all legal values, so that we have CMD = 2, CMD_OUT = 3 and so on.

I took a stub at documenting CMD and FLUSH request types in virtio block. Christoph, could you look over this please? I note that the interface seems full of warts to me, this might be a first step to cleaning them. One issue I struggled with especially is how type field mixes bits and non-bit values. I ended up simply defining all legal values, so that we have CMD = 2, CMD_OUT = 3 and so on.