| /qemu/qapi/ |
| H 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/system/ |
| H 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
150 - How the system boots, via firmware or direct kernel boot.
|
| H 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
|
| H 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
|
| H 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
|
| /qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 4 How backwards compatibility works
105 How do we tell QEMU about these device feature changes? In
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
229 How can we get this to work with migration. The way to do that is
302 configuration is correct. QEMU doesn't know how to look at this kind
317 How to mitigate when we have a backward compatibility error
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::
[all …]
|
| /qemu/docs/devel/ |
| H A D | multiple-iothreads.rst | 11 This document explains the ``IOThread`` feature and how to write code that runs
51 How to program for ``IOThread``\ s
97 How to synchronize with an ``IOThread``
125 `How to program for IOThreads`_ for information on how to do that.
|
| H A D | index-process.rst | 6 Notes about how to interact with the community and how and where to submit patches.
|
| H 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
|
| H A D | writing-monitor-commands.rst | 1 How to write monitor commands
4 This document is a step-by-step guide on how to write new QMP commands using
137 3. It takes an "Error \*\*" argument. This is required. Later we will see how to
166 # @times: how many times to print the message (default: 1)
303 former is the monitor object. The latter is how the monitor passes
333 Please check the "-monitor" command-line option to know how to open a user
648 This is how the actual HMP command is done.
|
| H 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
|
| H A D | rust.rst | 134 This section explains how to work with them.
227 Rust has very strict rules with respect to how you get an exclusive (``&mut``)
321 The ``vmstate`` module has examples of how to retrieve type information
421 slightly complicated process, mostly due to the need to teach Meson how
426 learn how to build them, as well as to the relevant ``Cargo.toml`` files.
436 Second, a new ``wrap`` file must be added to teach Meson how to download the
|
| /qemu/docs/devel/testing/ |
| H A D | index.rst | 4 Details about how to test QEMU and how it is integrated into our CI
|
| H 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
|
| H 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
|
| H A D | blkverify.rst | 7 This document describes how to use the ``blkverify`` protocol to test that a block
19 How it works
|
| /qemu/docs/system/s390x/ |
| H 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
|
| /qemu/docs/ |
| H A D | qcow2-cache.txt | 16 caches, and how to configure them.
45 There can be many L2 tables, depending on how much space has been
79 In order to choose the cache sizes we need to know how they relate to
112 How to configure the cache sizes
198 (as explained in the "Choosing the right cache sizes" and "How to
|
| H 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
|
| /qemu/docs/specs/ |
| H A D | ppc-spapr-numa.rst | 9 of the elements that impacts how QEMU views NUMA in pseries.
137 How the pseries Linux guest calculates NUMA distances
141 how the distances are expressed. The SLIT table provides the NUMA distance
184 `How the pseries Linux guest calculates NUMA distances`_. The result
193 This is how it is being done:
240 How associativity domains are assigned
399 regardless of how the ibm,associativity properties are being created in
|
| H A D | riscv-aia.rst | 34 The following table summarizes how the AIA and accelerator options defines what
38 .. list-table:: How AIA and accel options changes controller emulation
|
| /qemu/include/crypto/ |
| H A D | pbkdf.h | 113 * The @iterations count determines how many times
114 * the hashing process is run, which influences how
139 * Time the PBKDF2 algorithm to determine how many
|
| /qemu/hw/hyperv/ |
| H A D | hv-balloon-our_range_memslots.h | 25 /* How many pages were hot-added to the guest */
83 /* How many slots are currently mapped */
|
| /qemu/include/hw/mem/ |
| H A D | memory-device.h | 108 * Optional: Instruct the memory device to decide how many memory slots
157 * support automatically deciding how many memslots to use to only use a single
161 * cause problems, not even when devices automatically decided how many memslots
|
| /qemu/tests/qemu-iotests/ |
| H A D | 253 | 50 # We do not know how large a physical sector is, but it is certainly
67 # we do not know how large a physical sector is, so we just start
|