/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/devel/ |
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-build.rst | 4 Details about how QEMU's build system works and how it is integrated
|
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 | index-api.rst | 4 Details about how QEMU's various internal APIs. Most of these are
|
H A D | index-internals.rst | 4 Details about QEMU's various subsystems including how to add features to them.
|
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 | 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 | nested-papr.txt | 24 This document explains how a guest operating system can act as a 113 as the new PAPR API. This includes the new HCALL interface and how it
|
H A D | writing-monitor-commands.rst | 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.
|
/qemu/docs/system/ |
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 | 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
|
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
|
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 | linuxboot.rst | 6 This section explains how to launch a Linux kernel inside QEMU without
|
/qemu/docs/devel/migration/ |
H A D | index.rst | 4 This is the main entry for QEMU migration documentations. It explains how
|
H 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/ |
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
|
H A D | pcidevices.rst | 26 Instead, ``uid`` and ``fid`` determine how the device is presented to the guest
|
/qemu/io/ |
H A D | channel-tls.c | 372 QIOChannelShutdown how, in qio_channel_tls_shutdown() argument 377 qatomic_or(&tioc->shutdown, how); in qio_channel_tls_shutdown() 379 return qio_channel_shutdown(tioc->master, how, errp); in qio_channel_tls_shutdown()
|
/qemu/tests/avocado/acpi-bits/bits-config/ |
H A D | bits-cfg.txt | 17 # to see how these options are parsed and used.
|
/qemu/include/io/ |
H A D | channel.h | 145 QIOChannelShutdown how, 634 QIOChannelShutdown how,
|
/qemu/docs/ |
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/linux-user/ |
H A D | signal-common.h | 70 int do_sigprocmask(int how, const sigset_t *set, sigset_t *oldset);
|
/qemu/tests/vm/ |
H A D | conf_example_aarch64.yml | 24 # The below is a example for how to configure NUMA topology with
|