External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-03-07 17:28:15 +00:00
Code

Fix spelling

Browse Source 
Signed-off-by: Tim Wiederhake <twiederh@redhat.com>
This commit is contained in:
Tim Wiederhake 2022-11-11 16:48:48 +01:00
parent f81ee7b549
commit aee64348eb
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
NEWS.rst
View File

@ -218,7 +218,7 @@ v8.5.0 (2022-07-01)
* qemu: Add support for zero-copy migration * qemu: Add support for zero-copy migration
With QEMU 7.1.0, libvirt can enable zerocopy for parallel migration. This With QEMU 7.1.0, libvirt can enable zerocopy for parallel migration. This
is implmented by adding a new ``VIR_MIGRATE_ZEROCOPY`` flag(``virsh migrate is implemented by adding a new ``VIR_MIGRATE_ZEROCOPY`` flag(``virsh migrate
--zerocopy``). --zerocopy``).
* Introduce thread_pool_min and thread_pool_max attributes to IOThread * Introduce thread_pool_min and thread_pool_max attributes to IOThread

2
src/qemu/qemu.conf.in
View File

@ -963,7 +963,7 @@
# "vcpus" - only QEMU vCPU threads are placed into a separate scheduling group, # "vcpus" - only QEMU vCPU threads are placed into a separate scheduling group,
# emulator threads and helper processes remain outside of the group # emulator threads and helper processes remain outside of the group
# "emulator" - only QEMU and its threads (emulator + vCPUs) are placed into # "emulator" - only QEMU and its threads (emulator + vCPUs) are placed into
# separate scheduling group, helper proccesses remain outside of # separate scheduling group, helper processes remain outside of
# the group # the group
# "full" - both QEMU and its helper processes are placed into separate # "full" - both QEMU and its helper processes are placed into separate
# scheduling group # scheduling group

2
src/qemu/qemu_monitor.c
View File

@ -4346,7 +4346,7 @@ qemuMonitorQueryStatsProviderNew(qemuMonitorQueryStatsProviderType provider_type
/* /*
* This can be lowered later in case of the enum getting quite large, hence * This can be lowered later in case of the enum getting quite large, hence
* the virBitmapSetExpand below which also incidently makes this function * the virBitmapSetExpand below which also incidentally makes this function
* non-fallible. * non-fallible.
*/ */
provider->names = virBitmapNew(QEMU_MONITOR_QUERY_STATS_NAME_LAST); provider->names = virBitmapNew(QEMU_MONITOR_QUERY_STATS_NAME_LAST);