| commit | 36d27d2120979db239230bb440c03d41dbe75165 | |
| author | Stefan Hajnoczi <stefanha@redhat.com> | |
| Wed, 23 Oct 2019 10:04:14 +0000 (23 11:04 +0100) | ||
| committer | Michael S. Tsirkin <mst@redhat.com> | |
| Fri, 25 Oct 2019 11:46:22 +0000 (25 07:46 -0400) | ||
| tree | 7db013100a2b661d830d08991689e6bad469658d | treesnapshot (tar.gz zip) |
| parent | e73255be96bf435fe6bf9a5c196dcd7c76adb0da | commitdiff |
tests/virtio-blk-test: set up virtqueue after feature negotiation
VIRTIO Device Initialization requires that feature negotiation has
completed before virtqueues are set up. This makes sense because the
driver must know whether it is operating in Legacy or VIRTIO 1.0 mode
before it can access vring fields with the correct endianness.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20191023100425.12168-6-stefanha@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
VIRTIO Device Initialization requires that feature negotiation has
completed before virtqueues are set up. This makes sense because the
driver must know whether it is operating in Legacy or VIRTIO 1.0 mode
before it can access vring fields with the correct endianness.
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Message-Id: <20191023100425.12168-6-stefanha@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
| tests/virtio-blk-test.c | diffblobblamehistory |