mirror of
https://github.com/Motorhead1991/qemu.git
synced 2025-08-03 07:43:54 -06:00
docs/: fix some comment spelling errors
I found that there are many spelling errors in the comments of qemu, so I used the spellcheck tool to check the spelling errors and finally found some spelling errors in the docs folder. Signed-off-by: zhaolichang <zhaolichang@huawei.com> Reviewed-by: Peter Maydell <peter.maydell@linaro.org> Message-Id: <20200917075029.313-4-zhaolichang@huawei.com> Signed-off-by: Laurent Vivier <laurent@vivier.eu>
This commit is contained in:
parent
3a4452d896
commit
76ca4b58c2
17 changed files with 27 additions and 27 deletions
|
@ -464,7 +464,7 @@ the ``VHOST_USER_SET_MEM_TABLE`` request. For invalidation events, the
|
|||
(3), the I/O virtual address and the size. On success, the slave is
|
||||
expected to reply with a zero payload, non-zero otherwise.
|
||||
|
||||
The slave relies on the slave communcation channel (see :ref:`Slave
|
||||
The slave relies on the slave communication channel (see :ref:`Slave
|
||||
communication <slave_communication>` section below) to send IOTLB miss
|
||||
and access failure events, by sending ``VHOST_USER_SLAVE_IOTLB_MSG``
|
||||
requests to the master with a ``struct vhost_iotlb_msg`` as
|
||||
|
@ -1450,7 +1450,7 @@ vhost-user backends can provide various devices & services and may
|
|||
need to be configured manually depending on the use case. However, it
|
||||
is a good idea to follow the conventions listed here when
|
||||
possible. Users, QEMU or libvirt, can then rely on some common
|
||||
behaviour to avoid heterogenous configuration and management of the
|
||||
behaviour to avoid heterogeneous configuration and management of the
|
||||
backend programs and facilitate interoperability.
|
||||
|
||||
Each backend installed on a host system should come with at least one
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue