Hi everyone,
this PATCH presents an updated version of the RFC virtio device spec for
the virtio-vhost-user device. The initial RFC implementation can be
found here: [1].
This PATCH is split into four parts:
1. the first commit is just a refactored version of the initial RFC
implementation [1]. I just moved the device spec into a separate .tex
file and changed the device id from #24 to #28 since the ids #24-#27 are
reserved.
2. the second commit fixes some minor issues with the device spec. This
is quite straightforward.
3. the third commit enhances the notification capability with some
device/driver requirements. This makes sense because the notification
capability behaves similarly to the MSI-X capability, thereby having
some requirements that need to be mentioned.
4. the fourth commit synchronizes the shared memory capability with a
recent patch [2] that attempts to standardize a standalone
SHARED_MEMORY_CFG virtio capability.
v3 changes:
* Device Requirements for the Notification Capability: point out the
difference between the MSI-X Table Size stored in the Message Control
register of the MSI-X capability structure and the actual MSI-X Table
Size
v2 changes:
* Change device id from #25 to #28
Looking forward to your comments.
Thanks,
Nikos
[1] https://lists.oasis-open.org/archives/virtio-dev/201801/msg00110.html
[2] https://lists.oasis-open.org/archives/virtio-dev/201902/msg00142.html
Nikos Dragazis (3):
vhost-user: minor fixes
vhost-user: add requirements for the notification capability
vhost-user: update shared memory capability
Stefan Hajnoczi (1):
vhost-user: add vhost-user device type
content.tex | 3 +
introduction.tex | 1 +
virtio-vhost-user.tex | 349 ++++++++++++++++++++++++++++++++++++++++++++++++++
3 files changed, 353 insertions(+)
create mode 100644 virtio-vhost-user.tex
--
2.7.4
