Home
last modified time | relevance | path

Searched refs:both (Results 1 – 25 of 191) sorted by relevance

12345678

/qemu/hw/hyperv/
H A Dtrace-events31 …t64_t count, uint64_t start, unsigned int both) "processing remove response range %"PRIu64" @ 0x%"…
32 …r, unsigned int both) "response range hole %"PRIu64" @ 0x%"PRIx64" from range %"PRIu64" @ 0x%"PRIx…
33 …int both) "response common range %"PRIu64" @ 0x%"PRIx64" from range %"PRIu64" @ 0x%"PRIx64" with o…
34 …t64_t count, uint64_t start, unsigned int both) "remove response remaining range %"PRIu64" @ 0x%"P…
H A Dhv-balloon-our_range_memslots.h53 bool both) in our_range_get_removed_tree() argument
55 if (both) { in our_range_get_removed_tree()
63 bool both) in our_range_is_removed_tree_empty() argument
65 if (both) { in our_range_is_removed_tree_empty()
H A Dhv-balloon.c734 bool both, in hv_balloon_remove_response_handle_range() argument
739 both ? balloon->removed_both : balloon->removed_guest; in hv_balloon_remove_response_handle_range()
741 both ? &balloon->removed_both_ctr : &balloon->removed_guest_ctr; in hv_balloon_remove_response_handle_range()
748 trace_hv_balloon_remove_response(range->count, range->start, both); in hv_balloon_remove_response_handle_range()
758 PageRangeTree ourtree = our_range_get_removed_tree(our_range, both); in hv_balloon_remove_response_handle_range()
770 rangeeff.start, both); in hv_balloon_remove_response_handle_range()
785 both); in hv_balloon_remove_response_handle_range()
799 both); in hv_balloon_remove_response_handle_range()
808 bool both, in hv_balloon_remove_response_handle_pages() argument
818 hv_balloon_remove_response_handle_range(balloon, range, both, in hv_balloon_remove_response_handle_pages()
/qemu/tests/qemu-iotests/
H A D133.out30 qemu-io: Cannot set both -r/-w and 'read-only'
31 qemu-io: Cannot set both -r/-w and 'read-only'
32 qemu-io: Cannot set both -c and the cache options
33 qemu-io: Cannot set both -c and the cache options
34 qemu-io: Cannot set both -c and the cache options
H A D19188 echo === Check that both top and top2 point to base now ===
136 echo === Check that both top and top2 point to base now ===
/qemu/linux-user/ppc/
H A DMakefile.vdso9 -Wl,-h,linux-vdso32.so.1 -Wl,--hash-style=both \
12 -Wl,-h,linux-vdso64.so.1 -Wl,--hash-style=both \
/qemu/docs/devel/migration/
H A Dcompatibility.rst30 machine type in both source and destination. The QEMU hardware
54 we have the same QEMU version in both sides (qemu-5.2) but we are using
62 both sides are the same QEMU and both sides have exactly the same
70 Now it comes the interesting ones, when both QEMU processes are
167 Here we have the same QEMU in both sides. So it doesn't matter a
220 A device with different features on both sides
223 Let's assume that we are using the same QEMU binary on both sides,
225 different features on both sides of the migration. That can be
226 because the devices are different, because the kernel driver of both
233 features of both sides, and that is the way that you should launch
[all …]
H A Dpostcopy.rst22 To enable postcopy, issue this command on the monitor (both source and
38 That metric is calculated both for all vCPUs as overlapped value, and
206 fail a migration because VM data resides in both source and destination
207 QEMU instances. On the other hand, when issue happens QEMU on both sides
213 - When network issue occurs, both QEMU will go into **POSTCOPY_PAUSED**
225 - When both sides of QEMU successfully reconnect using a new or fixed up
234 postcopy migration on both sides and go back to **POSTCOPY_ACTIVE**
256 identical; i.e. RAMBlocks on both sides must use the same page size.
/qemu/qapi/
H A Daudio.json16 # General audio backend options that are used for both playback and
91 # Options of the ALSA backend that are used for both playback and
154 # Options of the Core Audio backend that are used for both playback
205 # Options of the JACK backend that are used for both playback and
255 # Options of the OSS backend that are used for both playback and
307 # Options of the Pulseaudio backend that are used for both playback
351 # Options of the PipeWire backend that are used for both playback and
392 # Options of the SDL audio backend that are used for both playback and
/qemu/docs/system/i386/
H A Dmicrovm.rst9 for benchmarking and optimizing both QEMU and guest operating systems,
10 since it is optimized for both boot time and footprint.
70 By default, microvm aims for maximum compatibility, enabling both
89 ``TSC_DEADLINE`` feature, you can also disable both the i8259 PIC and
/qemu/docs/system/
H A Dtls.rst94 Thus it is recommended that the server certificate include both the
201 If a single host is going to be using TLS in both a client and server
202 role, it is possible to create a single certificate to cover both roles.
206 a single certificate, simply include the template data from both the
211 # cat > both-hostNNN.info <<EOF
228 # certtool --generate-privkey > both-hostNNN-key.pem
232 --load-privkey both-hostNNN-key.pem \
233 --template both-hostNNN.info \
234 --outfile both-hostNNN-cert.pem
H A Dtarget-xtensa.rst6 Two executables cover simulation of both Xtensa endian options,
/qemu/docs/devel/
H A Dmultiple-iothreads.rst17 event loop. The VNC server and the QMP monitor are both processed from the
25 Side note: The main loop and ``IOThread`` are both event loops but their code is
94 works both in ``IOThread``\ s or the main loop, depending on which ``AioContext``
130 (via ioeventfd). To achieve both objects, wrap the code between
/qemu/docs/system/devices/
H A Divshmem-flat.rst12 Similar to the ivshmem device, the ivshmem-flat device supports both peer
25 Although the ivshmem-flat supports both peer notification (interrupts) and
/qemu/linux-user/x86_64/
H A DMakefile.vdso10 -Wl,--build-id=sha1 -Wl,--hash-style=both \
/qemu/linux-user/hppa/
H A DMakefile.vdso10 -Wl,--build-id=sha1 -Wl,--hash-style=both \
/qemu/linux-user/s390x/
H A DMakefile.vdso10 -Wl,--build-id=sha1 -Wl,--hash-style=both \
/qemu/linux-user/i386/
H A DMakefile.vdso10 -Wl,--build-id=sha1 -Wl,--hash-style=both \
/qemu/linux-user/loongarch64/
H A DMakefile.vdso10 -Wl,--build-id=sha1 -Wl,--hash-style=both \
/qemu/tests/qtest/migration/
H A DMakefile28 * inside tests/migration to update, and then remember to send both
/qemu/linux-user/aarch64/
H A DMakefile.vdso9 -Wl,--build-id=sha1 -Wl,--hash-style=both \
H A Dmeson.build3 # both header files and include the right one via #if.
/qemu/linux-user/riscv/
H A DMakefile.vdso9 -Wl,--hash-style=both -Wl,-T,$(SUBDIR)/vdso.ld
/qemu/docs/interop/
H A Dvhost-vdpa.rst9 specific control path. vDPA devices can be both physically located on
/qemu/linux-user/arm/
H A Dmeson.build11 # both header files and include the right one via #if.

12345678