diff options
| author | Sebastien Boeuf <sebastien.boeuf@intel.com> | 2021-06-08 14:55:22 +0200 |
|---|---|---|
| committer | Sebastien Boeuf <sebastien.boeuf@intel.com> | 2021-06-16 14:53:09 +0200 |
| commit | e294ed66fcc12e033957f20034ae5fef5bb9eeac (patch) | |
| tree | 3ebaa66600b522cfa998d0f9cf906953e5d4c5a4 /coverage_config_x86_64.json | |
| parent | a8ff939161d41fc2f449b80e461d013c1e19f666 (diff) | |
| download | vmm_vhost-e294ed66fcc12e033957f20034ae5fef5bb9eeac.tar.gz | |
vhost_user: Fix NEED_REPLY for all messages
Except the list of commands from which we can expect a reply, all the
other commands should be able to reply with an acknowledgment if being
asked for.
For the commands such as SET_PROTOCOL_FEATURES, which usually happens
before the protocol features negotiation is complete, we should also be
able to reply with an ACK if needed. Indeed, the protocol features
negotiation could have happened earlier, which means we might expect a
reply ACK from GET_FEATURES command if this happens later on.
Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
Diffstat (limited to 'coverage_config_x86_64.json')
0 files changed, 0 insertions, 0 deletions