Searched refs:tracking (Results 1 – 21 of 21) sorted by relevance
/qemu/hw/vfio/ |
H A D | common.c | 986 control->num_ranges = !!tracking->max32 + !!tracking->max64 + in vfio_device_feature_dma_logging_start_create() 987 !!tracking->maxpci64; in vfio_device_feature_dma_logging_start_create() 998 if (tracking->max32) { in vfio_device_feature_dma_logging_start_create() 1000 ranges->length = (tracking->max32 - tracking->min32) + 1; in vfio_device_feature_dma_logging_start_create() 1003 if (tracking->max64) { in vfio_device_feature_dma_logging_start_create() 1005 ranges->length = (tracking->max64 - tracking->min64) + 1; in vfio_device_feature_dma_logging_start_create() 1008 if (tracking->maxpci64) { in vfio_device_feature_dma_logging_start_create() 1010 ranges->length = (tracking->maxpci64 - tracking->minpci64) + 1; in vfio_device_feature_dma_logging_start_create() 1014 tracking->min32, tracking->max32, in vfio_device_feature_dma_logging_start_create() 1015 tracking->min64, tracking->max64, in vfio_device_feature_dma_logging_start_create() [all …]
|
/qemu/docs/devel/migration/ |
H A D | vfio.rst | 92 System memory dirty pages tracking 96 the VFIO dirty tracking module to start and stop dirty page tracking. A 98 dirty tracking module and marks system memory pages which were DMA-ed by the 101 Currently there are two ways dirty page tracking can be done: 102 (1) Device dirty tracking: 104 method can be used only if the device is capable of tracking its DMAs. 105 Discovering device capability, starting and stopping dirty tracking, and 113 In this method dirty tracking is done by IOMMU. However, there is currently no 114 IOMMU support for dirty page tracking. For this reason, all pages are 133 System memory dirty pages tracking when vIOMMU is enabled [all …]
|
H A D | mapped-ram.rst | 66 depends on async dirty tracking (KVM_GET_DIRTY_LOG) which is not
|
H A D | CPR.rst | 16 thus does not depend on any form of dirty page tracking.
|
/qemu/qapi/ |
H A D | vfio.json | 26 # @pre-copy: The device is running, tracking its internal state and its 30 # tracking its internal state and its internal state is available
|
H A D | ui.json | 1154 # @tracking-id: ID to correlate this event with previously generated 1166 'tracking-id': 'int',
|
H A D | block-core.json | 2233 # @node: name of device/node which the bitmap is tracking 2245 # @node: name of device/node which the bitmap is tracking 2284 # @node: name of device/node which the @target bitmap is tracking 2301 # Create a dirty bitmap with a name on the node, and start tracking 2323 # Stop write tracking and remove the dirty bitmap that was created 2370 # Enables a dirty bitmap so that it will begin tracking disk changes. 2391 # Disables a dirty bitmap so that it will stop tracking disk changes.
|
/qemu/docs/interop/ |
H A D | qcow2.txt | 309 type: the dirty tracking bitmap, which tracks virtual disk changes from some 778 type of this bitmap must be 'dirty tracking bitmap'. 794 1: Dirty tracking bitmap 889 === Dirty tracking bitmaps === 891 Bitmaps with 'type' field equal to one are dirty tracking bitmaps. 893 When the virtual disk is in use dirty tracking bitmap may be 'enabled' or 905 tracking virtual disk changes to this bitmap from the first write to the
|
H A D | bitmaps.rst | 35 Smaller granularities mean more accurate tracking of modified disk data, but 48 explicitly added in order to begin tracking writes. 63 QEMU also supports the migration of both transient bitmaps (tracking any
|
H A D | vhost-user.rst | 737 Inflight I/O tracking
|
/qemu/docs/devel/ |
H A D | tcg.rst | 190 Finally, the MMU helps tracking dirty pages and pages pointed to by
|
H A D | submitting-a-patch.rst | 512 tracking a good summary across versions. Also, the `git-backport-diff 563 <http://patchew.org/QEMU/>`__ includes a web interface for tracking the
|
H A D | multi-thread-tcg.rst | 183 - Dirty page tracking (for code gen, SMC detection, migration and display)
|
H A D | memory.rst | 15 - tracking RAM changes by the guest
|
H A D | tcg-plugins.rst | 491 of these options to limit the tracking to just one class of accesses.
|
H A D | qapi-code-gen.rst | 757 for the generator, which uses them for unions and for tracking
|
/qemu/ |
H A D | configure | 698 --disable-dependency-tracking|\
|
H A D | MAINTAINERS | 24 Q: Patchwork web based patch tracking system site
|
/qemu/docs/ |
H A D | rdma.txt | 415 3. Also, some form of balloon-device usage tracking would also
|
/qemu/pc-bios/ |
H A D | edk2-licenses.txt | 292 control systems, and issue tracking systems that are managed by, 513 control systems, and issue tracking systems that are managed by,
|
/qemu/target/i386/tcg/ |
H A D | decode-new.c.inc | 2778 * cause incorrect tracking of CC_OP for instructions that write to both memory
|