Home
last modified time | relevance | path

Searched full:layer (Results 1 – 25 of 169) sorted by relevance

1234567

/qemu/tests/qemu-iotests/
H A D198.out11 == writing whole image layer ==
19 == verify pattern layer ==
23 == committing layer into base ==
30 == verify pattern layer ==
78 == checking image layer ==
H A D19870 echo "== writing whole image layer =="
78 echo "== verify pattern layer =="
82 echo "== committing layer into base =="
90 echo "== verify pattern layer =="
102 echo "== checking image layer =="
H A D14473 # First live snapshot, new overlay as active layer
83 echo === Performing block-commit on active layer ===
88 # Block commit on active layer, push the new overlay into base
113 # New live snapshot, new overlays as active layer
H A D09750 # 0: Two-layer backing chain, commit to upper backing file (implicitly)
52 # 1: Two-layer backing chain, commit to upper backing file (explicitly)
54 # 2: Two-layer backing chain, commit to upper backing file (implicitly with -d)
56 # 3: Two-layer backing chain, commit to lower backing file
H A D154128 # Active layer: -- 00 00 --
136 # Active layer: -- 00 00 --
144 # Active layer: -- 00 00 --
152 # Active layer: -- 00 00 --
227 # Active layer: -- -- XX 00 | 00 XX -- --
246 # Active layer: 64k: XX XX 00 00 | 00 00 00 00 | 00 -- -- --
262 # Active layer: 64k: -- -- 00 00 | 00 00 00 00 | 00 -- -- --
277 # Active layer: 64k: -- -- 00 00 | 00 00 00 00 | 00 -- XX XX
293 # Active layer: 64k: -- XX 00 00 | 00 00 00 00 | 00 XX XX --
429 # Active layer: 128m... | -- -- 00 --
[all …]
H A D17667 # 0: Two-layer backing chain, commit to upper backing file (implicitly)
69 # 1: Two-layer backing chain, commit to upper backing file (explicitly)
71 # 2: Two-layer backing chain, commit to upper backing file (implicitly with -d)
73 # 3: Two-layer backing chain, commit to lower backing file
H A D25876 # It is important to use raw for the base layer (so that
77 # permissions are just handed through to the protocol layer)
H A DREADME6 This package contains a simple test suite for the I/O layer of qemu.
/qemu/docs/devel/
H A Dzoned-storage.rst12 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 Dmultiple-iothreads.rst112 ``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 Dreplay.rst45 * 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
/qemu/hw/char/
H A Dsclpconsole.c41 uint32_t iov_bs; /* offset in buf for char layer read operation */
52 /* character layer call-back functions */ in DECLARE_INSTANCE_CHECKER()
75 /* put byte-stream from character layer into buffer */ in chr_read()
163 * - write console data to character layer
197 /* event buffer not accepted due to error in character layer */ in write_event_data()
222 /* tell character layer our call-back functions */
H A Dsclpconsole-lm.c46 uint32_t write_errors; /* errors writing to char layer */
57 * Character layer call-back functions in DECLARE_INSTANCE_CHECKER()
61 * Accumulate bytes from character layer in console buffer, in DECLARE_INSTANCE_CHECKER()
196 * - write console data to character layer
271 /* character layer error */ in write_event_data()
306 /* tell character layer our call-back functions */
/qemu/include/block/
H A Dblock-common.h207 * copied to the top layer (i.e., that COR operation is done).
240 ignoring the format layer */
251 /* Option names of options parsed by the block layer */
290 * BDRV_BLOCK_DATA: allocation for data at offset is tied to this layer
294 * layer rather than any backing, set by block layer
296 * layer, set by block layer
302 * that the block layer recompute the answer from the returned
304 * BDRV_BLOCK_RECURSE: request that the block layer will recursively search for
H A Dgraph-lock.h2 * Graph lock: rwlock to protect block layer graph manipulations (add/remove
25 * This API provides a rwlock used to protect block layer
104 * adding or removing an edge or a node in the block layer graph. Nobody else
H A Dqdict.h2 * Special QDict functions used by the block layer
H A Dqapi.h2 * Block layer qmp and info dump related functions
H A Dblock_int-common.h158 * blocks are not allocated in this layer of backing-chain
161 * - read from the backing file otherwise, where the block layer
618 * according to the current layer, and should only need to set
620 * and/or BDRV_BLOCK_RAW; if the current layer defers to a backing
621 * layer, the result should be 0 (and not BDRV_BLOCK_ZERO). The
627 * results. The block layer guarantees input clamped to
652 * in generic block-layer: no serializing, no alignment, no tracked
1220 * save_snaphost, but the block layer is quiescent during those.
/qemu/docs/interop/
H A Dnbd.rst44 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 Dlive-block-operations.rst13 QEMU Block Layer currently (as of QEMU 2.9) supports four major kinds of
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
[all …]
/qemu/include/qemu/
H A Dmain-loop.h266 * This function should never be used in the block layer, because
267 * unit tests, block layer tools and qemu-storage-daemon do not
290 * the global state of the block layer.
292 * Global state of the block layer is not accessible from I/O threads
295 * layer tools and qemu-storage-daemon there is a designated thread that
300 * as the block layer main thread; this will be any of the actual
303 * For clarity, do not use this function outside the block layer.
/qemu/ui/
H A Dvnc-auth-sasl.h37 /* If we want to negotiate an SSF layer with client */
39 /* If we are now running the SSF layer */
/qemu/hw/tpm/
H A Dtpm_tis_i2c.c77 * These registers are sent to TIS layer. The register with UNKNOWN
78 * mapping are not sent to TIS layer and handled in I2c layer.
469 * register value hence I2C layer cache the register value and send in tpm_tis_i2c_send()
/qemu/tests/qemu-iotests/tests/
H A Dqemu-img-bitmaps91 # Only bitmaps from the active layer are copied
106 echo "=== Merge from top layer into backing image ==="
/qemu/include/hw/xen/interface/
H A Dxen-compat.h5 * Guest OS interface to Xen. Compatibility layer.

1234567