aboutsummaryrefslogtreecommitdiff
path: root/scripts/symlink-install-tree.py
diff options
context:
space:
mode:
authorHanna Czenczek <hreitz@redhat.com>2023-10-16 15:42:39 +0200
committerMichael S. Tsirkin <mst@redhat.com>2023-11-07 03:39:10 -0500
commita6e76dd3c3b98db86802b4b08984f2ac5ec1faea (patch)
tree36eccfd79e3d7160bec1c626c3a9dc0d9afd7166 /scripts/symlink-install-tree.py
parenteae69cc36b278a3e84bb013909135e138b37855d (diff)
downloadqemu-a6e76dd3c3b98db86802b4b08984f2ac5ec1faea.zip
qemu-a6e76dd3c3b98db86802b4b08984f2ac5ec1faea.tar.gz
qemu-a6e76dd3c3b98db86802b4b08984f2ac5ec1faea.tar.bz2
vhost-user.rst: Introduce suspended state
In vDPA, GET_VRING_BASE does not stop the queried vring, which is why SUSPEND was introduced so that the returned index would be stable. In vhost-user, it does stop the vring, so under the same reasoning, it can get away without SUSPEND. Still, we do want to clarify that if the device is completely stopped, i.e. all vrings are stopped, the back-end should cease to modify any state relating to the guest. Do this by calling it "suspended". Suggested-by: Stefan Hajnoczi <stefanha@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Hanna Czenczek <hreitz@redhat.com> Message-Id: <20231016134243.68248-4-hreitz@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'scripts/symlink-install-tree.py')
0 files changed, 0 insertions, 0 deletions