| /qemu/docs/specs/ |
| H A D | ppc-spapr-hotplug.rst | 33 for hot plugged resources described under :ref:`guest-host-interface`.
35 The array properties are described below. Each entry/element in an array
328 The format for these EPOW-signalled events is described below under
331 also described below under :ref:`hot-plug-unplug-event-structure`, and so are
339 ``ibm,architecture-vec-5`` option vector structure (as described by [LoPAR]_,
344 guest's device tree using the standard format described in [LoPAR]_,
450 described here.
487 ``ibm,associativity-lookup-arrays`` property described earlier. This is used
507 ``ibm,associativity-lookup-arrays`` property described earlier. This
|
| H A D | acpi_cpu_hotplug.rst | 39 All accesses to registers described below, imply little-endian byte order.
139 Firmware shall issue device eject request as described above
|
| H A D | vmw_pvscsi-spec.rst | 28 registers area is described by the ``PVSCSIRegOffset`` enum. There
|
| H A D | fsi.rst | 24 an internal Local Bus (LBUS) which is described by the CFAM configuration
|
| /qemu/docs/ |
| H A D | rdma.txt | 183 6. Check versioning and capabilities (described later)
186 which is described by a formal protocol. Each SEND message has a
261 of the connection (described below).
264 described above all use the aforementioned two functions to do the hard work:
276 3. Also, the QEMUFile interfaces also call these functions (described below)
|
| H A D | throttle.txt | 82 the six basic parameters described in the previous section, but in
262 infrastructure described above but can be used anywhere in the node
268 described earlier in "Applying I/O limits to groups of disks".
329 The scenario described so far is very simple but the throttle block
|
| /qemu/pc-bios/ |
| H A D | README | 72 are described by the JSON documents in the "pc-bios/descriptors" directory,
83 source code also contains code reused from other projects described here:
|
| /qemu/include/hw/xen/interface/ |
| H A D | sched.h | 28 * @arg == Operation-specific extra argument(s), as described below.
29 * ... == Additional Operation-specific extra arguments, described below.
|
| /qemu/qapi/ |
| H A D | misc-arm.json | 14 # @version: version of GIC to be described. Currently, only 2 and 3
|
| /qemu/docs/interop/ |
| H A D | parallels.rst | 221 The dirty bitmap described by this feature extension is stored in a set of
224 entry is a 64 bit integer as described below:
|
| H A D | qcow2.rst | 552 offset is 0, the L2 table and all clusters described by this
643 The first 64 bits have the same format as the standard L2 table entry described
721 described by first L1 table entry that doesn't describe a
777 Each bitmap saved in the image is described in a bitmap directory entry. The
787 (described below) for the bitmap starts. Must be aligned to
895 As noted above, bitmap data is stored in separate clusters, described by the
|
| /qemu/docs/devel/ |
| H A D | multi-process.rst | 8 may lack features or be considerably different from what is described
33 QEMU can be broadly described as providing three main services. One is a
116 various ways, some of which are described below.
436 command described above. In either case, the remote process proxy will
586 described below attempt to ameliorate this effect by allowing the
723 descriptor are described below.
967 scheme described above. In this scenario, different categories would be
|
| H A D | tcg.rst | 55 main loop as described above. These mechanisms are:
98 optimized form described earlier in this section.
|
| /qemu/system/ |
| H A D | globals.c | 63 * little-endian "wire format" described in the SMBIOS 2.6 specification.
|
| /qemu/hw/misc/ |
| H A D | arm_integrator_debug.c | 8 * The real h/w is described at:
|
| /qemu/docs/system/ |
| H A D | replay.rst | 61 for every enabled block device, as described in :ref:`block-label` section.
64 it should be configured explicitly with replay filter, as described
|
| /qemu/linux-headers/linux/ |
| H A D | vfio.h | 186 * Return a new file descriptor for the device object described by
514 * actions described below.
634 * between described ranges are unimplemented.
842 * described by the provided dmabuf_id. The dmabuf_id is returned from VFIO_
1039 * ioctl as described above.
1064 * The device migration Finite State Machine is described by the enum
1107 * optionally go to the ERROR state as described below.
1110 * described above.
1143 * RUNNING, P2P quiesced or in STOP. The STOP_COPY state is described below
|
| /qemu/docs/system/arm/ |
| H A D | sabrelite.rst | 69 the mx6qsabrelite_defconfig with similar commands as described above for Linux:
|
| /qemu/tests/qemu-iotests/ |
| H A D | 115 | 51 # number of clusters which can be described by a single refblock; therefore, at
|
| /qemu/include/standard-headers/linux/ |
| H A D | virtio_config.h | 91 * device are ordered in a way described by the platform.
|
| /qemu/docs/system/devices/ |
| H A D | cxl.rst | 79 using means described in the CXL 2.0 specification.
99 space is described to system software via a CXL Host Bridge
399 OS management of CXL memory devices as described here.
|
| /qemu/include/crypto/ |
| H A D | akcipher.h | 33 * Determine if asymmetric key cipher described with @opts is
|
| /qemu/hw/intc/ |
| H A D | arm_gicv2m.c | 22 /* This file implements an emulated GICv2m widget as described in the ARM
|
| /qemu/hw/acpi/ |
| H A D | pcihp.c | 86 /* hotplugged bridges can't be described in ACPI ignore them */ in acpi_set_bsel()
173 * (and so, not described by acpi). in acpi_pcihp_pc_no_hotplug()
|
| /qemu/target/arm/tcg/ |
| H A D | psci.c | 61 * Coordination Interface (PSCI) calls (as described in ARM DEN 0022D.b), in arm_handle_psci_call()
|