| /qemu/qapi/ |
| A D | compat.json | 52 # @deprecated-input: how to handle deprecated input (default 'accept')
54 # @deprecated-output: how to handle deprecated output (default
57 # @unstable-input: how to handle unstable input (default 'accept')
60 # @unstable-output: how to handle unstable output (default 'accept')
|
| /qemu/docs/devel/testing/ |
| A D | index.rst | 4 Details about how to test QEMU and how it is integrated into our CI
|
| A D | ci-jobs.rst.inc | 13 For further information about how to set these variables, please refer to::
29 For further information about how to set these variables, please refer to::
81 base.yml and need to validate how they will operate when in
|
| A D | acpi-bits.rst | 20 how by being as close to the bios on a running system as possible without a
77 to alter how QEMU is spawned etc. Test writers typically would not need to
104 This location contains biosbits configuration files that determine how the
|
| /qemu/docs/devel/ |
| A D | index-process.rst | 6 Notes about how to interact with the community and how and where to submit patches.
|
| A D | index.rst | 17 :ref:`development_process` and how the community interacts. Please pay
22 through the :ref:`qom` documentation to understand how QEMU's object
|
| A D | index-api.rst | 4 Details about how QEMU's various internal APIs. Most of these are
|
| A D | index-build.rst | 4 Details about how QEMU's build system works. You will need to understand
|
| A D | index-internals.rst | 4 Details about QEMU's various subsystems including how to add features to them.
|
| A D | tcg-icount.rst | 12 with cycle accurate emulation - QEMU does not attempt to emulate how
37 executed. The budget of instructions is limited by how long it will be
|
| /qemu/docs/system/ |
| A D | device-emulation.rst | 18 A device front end is how a device is presented to the guest. The type
26 A front end is often paired with a back end, which describes how the
56 The back end describes how the data from the emulated device will be
61 by ``--blockdev`` which will specify how blocks are handled, for
|
| A D | introduction.rst | 143 - Backends are how QEMU deals with the guest's data, for example
144 how a block device is stored, how network devices see the
145 network or how a serial device is directed to the outside world.
147 - How the system is displayed, how it is managed and controlled or
|
| A D | multi-process.rst | 6 This document describes how to configure and use multi-process qemu.
40 - The remaining options are no different from how one launches QEMU with
|
| A D | vm-templating.rst | 4 This document explains how to use VM templating in QEMU.
6 For now, the focus is on VM memory aspects, and not about how to save and
30 Please be aware of these implications and how to mitigate them for your
|
| A D | linuxboot.rst | 6 This section explains how to launch a Linux kernel inside QEMU without
|
| /qemu/docs/devel/migration/ |
| A D | index.rst | 4 This is the main entry for QEMU migration documentations. It explains how
|
| A D | compatibility.rst | 143 So, how can we address this problem. Easy, just convince qemu-5.2
190 Now, how was this done in reality? The following commit shows how it
302 configuration is correct. QEMU doesn't know how to look at this kind
325 Let see how it worked with one example.
375 The patch changes how we configure PCI space for AER. But QEMU fails
379 The following commit shows how this got fixed::
409 Now we see how the fix is done. This is going to depend on what kind
|
| /qemu/docs/system/s390x/ |
| A D | cpu-topology.rst | 21 how to enable it and explains the new CPU attributes.
22 For information on how to modify the S390 CPU topology and how to
29 See :ref:`Accelerators` for more details about accelerators and how to select them.
172 The polarization affects how the CPUs of a shared host are utilized/distributed
|
| A D | pcidevices.rst | 26 Instead, ``uid`` and ``fid`` determine how the device is presented to the guest
|
| /qemu/io/ |
| A D | channel-tls.c | 362 QIOChannelShutdown how, in qio_channel_tls_shutdown() argument
367 qatomic_or(&tioc->shutdown, how); in qio_channel_tls_shutdown()
369 return qio_channel_shutdown(tioc->master, how, errp); in qio_channel_tls_shutdown()
|
| /qemu/linux-user/ |
| A D | strace.c | 2839 abi_ulong sockfd, how; in do_print_shutdown() local
2842 get_user_ualx(how, arg1, 1); in do_print_shutdown()
2846 switch (how) { in do_print_shutdown()
3353 const char *how = "UNKNOWN"; in print_rt_sigprocmask() local
3360 qemu_log("%s,", how); in print_rt_sigprocmask()
3608 struct open_how_ver0 how; in print_openat2() local
3615 copy_struct_from_user(&how, sizeof(how), arg2, arg3) == 0) { in print_openat2()
3616 how.flags = tswap64(how.flags); in print_openat2()
3617 how.mode = tswap64(how.mode); in print_openat2()
3618 how.resolve = tswap64(how.resolve); in print_openat2()
[all …]
|
| A D | signal-common.h | 70 int do_sigprocmask(int how, const sigset_t *set, sigset_t *oldset);
|
| /qemu/tests/functional/acpi-bits/bits-config/ |
| A D | bits-cfg.txt | 17 # to see how these options are parsed and used.
|
| /qemu/include/io/ |
| A D | channel.h | 145 QIOChannelShutdown how,
637 QIOChannelShutdown how,
|
| /qemu/docs/ |
| A D | memory-hotplug.txt | 4 This document explains how to use the memory hotplug feature in QEMU,
12 In order to be able to hotplug memory, QEMU has to be told how many
|