Searched refs:layer (Results 1 – 25 of 43) sorted by relevance
12
/qemu/tests/qemu-iotests/ |
H A D | 198.out | 11 == writing whole image layer == 19 == verify pattern layer == 23 == committing layer into base == 30 == verify pattern layer == 78 == checking image layer ==
|
H A D | 144 | 83 echo === Performing block-commit on active layer ===
|
H A D | README | 6 This package contains a simple test suite for the I/O layer of qemu.
|
H A D | 144.out | 21 === Performing block-commit on active layer ===
|
H A D | 085 | 208 echo === Invalid command - snapshot node used as active layer ===
|
H A D | 051 | 264 echo === Specifying the protocol layer ===
|
H A D | 085.out | 181 === Invalid command - snapshot node used as active layer ===
|
/qemu/docs/devel/ |
H A D | zoned-storage.rst | 12 1. Block layer APIs for zoned storage 14 QEMU block layer supports three zoned storage models: 26 block layer while processing I/O requests. A BlockBackend has a root pointer to 32 The block layer APIs support commands needed for zoned storage devices, 38 like the virtio-blk emulation or the qemu-io-cmds.c utility can use block layer
|
H A D | multiple-iothreads.rst | 112 ``AioContext`` and the block layer 114 The ``AioContext`` originates from the QEMU block layer, even though nowadays 117 The block layer has support for ``AioContext`` integrated. Each 120 This allows block layer code to process I/O inside the 123 Block layer code must therefore expect to run in an ``IOThread`` and avoid using
|
H A D | block-coroutine-wrapper.rst | 5 A lot of functions in QEMU block layer (see ``block/*``) can only be
|
H A D | replay.rst | 45 * block driver for making block layer deterministic 185 requests proceed to block layer which creates "bottom halves". Bottom 197 Sometimes the block layer uses asynchronous callbacks for its internal purposes
|
H A D | vfio-iommufd.rst | 104 management layer. In such a case the fd is passed, the fd supports a
|
/qemu/docs/interop/ |
H A D | nbd.rst | 44 depth of which layer in a thin-provisioned backing chain provided the 45 data (0 for unallocated, 1 for the active layer, 2 for the first 46 backing layer, and so forth).
|
H A D | live-block-operations.rst | 51 is also referred to as the "active layer". 77 QEMU block layer supports. 100 (i.e. merge the current active layer into the base image). 180 overlay images; image [D] is the active layer -- i.e. live QEMU is 218 We have *three* points in time and an active layer: 224 - Active layer: Current guest state is contained in [A] + [B] + [C] + 250 (1) Merge everything into the active layer: I.e. copy all contents from 261 only images [B] and [C] into [D], the active layer. The result will 286 active layer, where 'node-D' is the current active image (by default 332 commit" (i.e. it is possible to merge the "active layer", the right-most [all …]
|
/qemu/docs/spin/ |
H A D | win32-qemu-event.promela | 30 /* Full model: layer a userspace-only fast path on top of the RAW_*
|
/qemu/tests/qemu-iotests/tests/ |
H A D | qemu-img-bitmaps.out | 61 === Merge from top layer into backing image ===
|
/qemu/docs/devel/migration/ |
H A D | uadk-compression.rst | 21 UADK consists of UACCE, vendors' drivers, and an algorithm layer. UADK requires
|
/qemu/hw/ide/ |
H A D | atapi.c | 488 int layer = packet[6]; in ide_dvd_read_structure() local 491 if (layer != 0) in ide_dvd_read_structure()
|
/qemu/docs/specs/ |
H A D | ppc-xive.rst | 20 processing layer of external interrupts:
|
/qemu/docs/system/ |
H A D | vnc-security.rst | 122 configured. If the chosen mechanism also provides a SSF layer, then it
|
H A D | introduction.rst | 52 There is a full :ref:`featured block layer<Live Block Operations>`
|
H A D | gdb.rst | 86 parallel flows of execution is a two layer one: it supports multiple
|
/qemu/docs/ |
H A D | block-replication.txt | 122 In case 1 and 5, we just report the error to the disk layer. In case 2, 3,
|
/qemu/ui/ |
H A D | cocoa.m | 385 [[self layer] addSublayer:cursorLayer]; 702 * layer. 703 * When cocoa_display_init() does register the dcl, the UI layer
|
/qemu/docs/devel/testing/ |
H A D | main.rst | 184 ``make check-block`` runs a subset of the block layer iotests (the tests that 194 framework widely used to test block layer related features. It is higher level 231 layer. An iotest case is usually the choice for that. There are already many
|
12