*
* Traps - count traps
*
- * Count the number of interrupts (asyncronous events), exceptions (synchronous
+ * Count the number of interrupts (asynchronous events), exceptions (synchronous
* events) and host calls (e.g. semihosting) per cpu and report those counts on
* exit.
*/
``contrib/plugins/traps.c``
-This plugin counts the number of interrupts (asyncronous events), exceptions
+This plugin counts the number of interrupts (asynchronous events), exceptions
(synchronous events) and host calls (e.g. semihosting) per cpu.
Other emulation features
* Indicate where the original patch was obtained from (mailing list, bug
tracker, author's git repo, etc) when sending it for review
* Acknowledge the extra work of the new contributor by including their
- ``Signed-off-by`` in the patch in addition to the orignal author's
+ ``Signed-off-by`` in the patch in addition to the original author's
* Indicate who is responsible for what parts of the patch. This is typically
done via a note in the commit message, just prior to the new contributor's
``Signed-off-by``::
container images from a clean git checkout.
* eBPF: QEMU includes some generated eBPF machine code, since the required
- eBPF compilation tools are not broadly available on all targetted OS
+ eBPF compilation tools are not broadly available on all targeted OS
distributions. The corresponding eBPF C code for the binary is also
provided. This is a time-limited exception until the eBPF toolchain is
sufficiently broadly available in distros.
which certificates are used for a session.
The use of multiple sets of certificates is intended to allow an
-incremental transition to certificates using different crytographic
+incremental transition to certificates using different cryptographic
algorithms. This allows a newly deployed QEMU to introduce use of
stronger cryptographic algorithms that will be preferred when talking
-to other newly deployed QEMU instances, while retaining compatbility
+to other newly deployed QEMU instances, while retaining compatibility
with certificates issued to a historically deployed QEMU. This is
notably useful to support live migration from an old QEMU deployed
on older operating system releases, which may support fewer crypto
Given a new enough gnutls release, suitably integrated & configured with the
operating system crypto policies, QEMU is able to support post-quantum
-crytography on TLS enabled services, either exclusively or in a hybrid mode.
+cryptography on TLS enabled services, either exclusively or in a hybrid mode.
In exclusive mode, only a single set of certificates need to be configured
for QEMU, with PQC compliant algorithms. Such a QEMU configuration will only
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
In the OS configuration for system crypto algorithm priorities has
-enabled PQC, this can (optionally) be overriden in QEMU configuration
+enabled PQC, this can (optionally) be overridden in QEMU configuration
disable use of PQC using the ``priority`` parameter to the ``tls-creds-x509``
object::
VirtMachineState *vms = VIRT_MACHINE(obj);
if (!strcmp(value, "auto")) {
- vms->msi_controller = VIRT_MSI_CTRL_AUTO; /* Will be overriden later */
+ vms->msi_controller = VIRT_MSI_CTRL_AUTO; /* Will be overridden later */
} else if (!strcmp(value, "its")) {
vms->msi_controller = VIRT_MSI_CTRL_ITS;
} else if (!strcmp(value, "gicv2m")) {
typedef enum VirtMSIControllerType {
VIRT_MSI_CTRL_NONE,
- /* This value is overriden at runtime.*/
+ /* This value is overridden at runtime.*/
VIRT_MSI_CTRL_AUTO,
/* Legacy option: its=off provides a GICv2m when using GICv2 */
VIRT_MSI_LEGACY_OPT_ITS_OFF,
* Attempting to write a register with @buf smaller than the register size
* will result in a crash or other undesired behavior.
*
- * Returns true on sucess, false on failure.
+ * Returns true on success, false on failure.
*/
QEMU_PLUGIN_API
bool qemu_plugin_write_register(struct qemu_plugin_register *handle,
# the device to write to the target path only. Note that drive
# mirroring includes `drive-mirror`, `blockdev-mirror` and
# `block-commit` job (only in case of "active commit", when the node
-# being commited is used by the guest). The ability to complete is
+# being committed is used by the guest). The ability to complete is
# signaled with a `BLOCK_JOB_READY` event.
#
# This command completes an active background block operation
##
# @blockdev-set-active:
#
-# Activate or inactivate a block device. Use this to manage the
+# Activate or deactivate a block device. Use this to manage the
# handover of block devices on migration with qemu-storage-daemon.
#
# Activating a node automatically activates all of its child nodes
-# first. Inactivating a node automatically inactivates any of its
+# first. Deactivating a node automatically deactivates any of its
# child nodes that are not in use by a still active node.
#
-# @node-name: Name of the graph node to activate or inactivate. By
+# @node-name: Name of the graph node to activate or deactivate. By
# default, all nodes are affected by the operation.
#
# @active: true if the nodes should be active when the command returns
# the device to write to the target path only. Note that drive
# mirroring includes `drive-mirror`, `blockdev-mirror` and
# `block-commit` job (only in case of "active commit", when the node
-# being commited is used by the guest). The ability to complete is
+# being committed is used by the guest). The ability to complete is
# signaled with a `BLOCK_JOB_READY` event.
#
# This command completes an active background block operation
##
# @UefiVariable:
#
-# UEFI Variable. Check the UEFI specifification for more detailed
+# UEFI Variable. Check the UEFI specification for more detailed
# information on the fields.
#
# @guid: variable namespace GUID
Enable/disable list in DHCP/DHCPv6/NDP
``map-host-loopback``
- Addresse to refer to host
+ Address to refer to host
``map-guest-addr``
Addr to translate to guest's address
UDP ports to forward
``param=string``
- ``string`` will be passed to passt has a command line parameter,
- we can have multiple occurences of the ``param`` parameter to
+ ``string`` will be passed to passt as a command line parameter,
+ we can have multiple occurrences of the ``param`` parameter to
pass multiple parameters to passt.
For instance, to pass ``--trace --log=trace.log``:
projects / thirdparty / qemu.git / commitdiff
