docs: Fix some typos (most found by codespell)
Signed-off-by: Stefan Weil <sw@weilnetz.de> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Signed-off-by: Thomas Huth <thuth@redhat.com>
This commit is contained in:
parent
55d38d10b8
commit
963e64a486
@ -104,7 +104,7 @@ Primary side.
|
||||
COLO Proxy:
|
||||
Delivers packets to Primary and Seconday, and then compare the responses from
|
||||
both side. Then decide whether to start a checkpoint according to some rules.
|
||||
Please refer to docs/colo-proxy.txt for more informations.
|
||||
Please refer to docs/colo-proxy.txt for more information.
|
||||
|
||||
Note:
|
||||
HeartBeat has not been implemented yet, so you need to trigger failover process
|
||||
|
@ -666,12 +666,12 @@ Master message types
|
||||
Equivalent ioctl: VHOST_SET_VRING_ENDIAN
|
||||
Master payload: vring state description
|
||||
|
||||
Set the endianess of a VQ for legacy devices. Little-endian is indicated
|
||||
Set the endianness of a VQ for legacy devices. Little-endian is indicated
|
||||
with state.num set to 0 and big-endian is indicated with state.num set
|
||||
to 1. Other values are invalid.
|
||||
This request should be sent only when VHOST_USER_PROTOCOL_F_CROSS_ENDIAN
|
||||
has been negotiated.
|
||||
Backends that negotiated this feature should handle both endianesses
|
||||
Backends that negotiated this feature should handle both endiannesses
|
||||
and expect this message once (per VQ) during device configuration
|
||||
(ie. before the master starts the VQ).
|
||||
|
||||
|
@ -320,7 +320,7 @@ Here is the list of events that are written into the log:
|
||||
async event id from the following list:
|
||||
- REPLAY_ASYNC_EVENT_BH. Bottom-half callback. This event synchronizes
|
||||
callbacks that affect virtual machine state, but normally called
|
||||
asyncronously.
|
||||
asynchronously.
|
||||
Argument: 8-byte operation id.
|
||||
- REPLAY_ASYNC_EVENT_INPUT. Input device event. Contains
|
||||
parameters of keyboard and mouse input operations
|
||||
|
Loading…
Reference in New Issue
Block a user