The virtio-queue interface is updated to take into consideration error
cases and to export a single Queue.
This PR is RFC for 2 reasons:
The virtio-queue update is not yet merged & we do not have a release for the crate.
We need to decide what we do in respect to error handling. Is the user of the vhost-user-backend interface trusted? Do we want to use unwrap or do we want to propagate errors instead?
Requirements
Before submitting your PR, please make sure you addressed the following
requirements:
[x] All commits in this PR are signed (with git commit -s), and the commit
message has max 60 characters for the summary and max 75 characters for each
description line.
[x] All added/changed functionality has a corresponding unit/integration
test.
[x] Any newly added unsafe code is properly documented.
Summary of the PR
The virtio-queue interface is updated to take into consideration error cases and to export a single Queue.
This PR is RFC for 2 reasons:
Requirements
Before submitting your PR, please make sure you addressed the following requirements:
git commit -s), and the commit message has max 60 characters for the summary and max 75 characters for each description line.unsafecode is properly documented.