/qemu/tests/qemu-iotests/ |
H A D | 021.out | 5 -1 is not a valid pattern byte 8 -1 is not a valid pattern byte 11 -1 is not a valid pattern byte 14 -1 is not a valid pattern byte 17 -1 is not a valid pattern byte 20 -1 is not a valid pattern byte 23 300 is not a valid pattern byte 26 300 is not a valid pattern byte 29 300 is not a valid pattern byte 32 300 is not a valid pattern byte [all …]
|
/qemu/hw/sparc64/ |
H A D | sun4u_iommu.c | 101 baseaddr = is->regs[IOMMU_BASE >> 3]; in sun4u_translate_iommu() 195 IOMMUState *is = opaque; in iommu_mem_write() local 203 is->regs[IOMMU_CTRL >> 3] |= val << 32; in iommu_mem_write() 205 is->regs[IOMMU_CTRL >> 3] = val; in iommu_mem_write() 215 is->regs[IOMMU_BASE >> 3] |= val << 32; in iommu_mem_write() 217 is->regs[IOMMU_BASE >> 3] = val; in iommu_mem_write() 238 IOMMUState *is = opaque; in iommu_mem_read() local 244 val = is->regs[IOMMU_CTRL >> 3] >> 32; in iommu_mem_read() 246 val = is->regs[IOMMU_CTRL >> 3]; in iommu_mem_read() 254 val = is->regs[IOMMU_BASE >> 3] >> 32; in iommu_mem_read() [all …]
|
/qemu/docs/system/arm/ |
H A D | cpu-features.rst | 120 collection is valid. 142 above, the ``cortex-a57`` CPU type is also valid when KVM is enabled. 182 the virtual time adjustment is enabled (vtime is not *not* adjusted). 198 Since v5.2, kvm-steal-time is enabled by default when KVM is 199 enabled, the feature is supported, and the guest is 64-bit. 234 is used to enable or disable specific vector lengths, where ``N`` is the 248 2) If a vector length ``N`` is enabled, then, when KVM is enabled, all 271 an error is generated. 279 3) If SVE is enabled, then an error is generated when attempting to 292 6) When KVM is enabled, if the host does support SVE, then an error is [all …]
|
H A D | sbsa.rst | 5 board is a generic board platform that doesn't match any real hardware). 7 The hardware part is defined by two specifications: 15 It is intended to be a machine for developing firmware and testing 46 platform using minimalistic devicetree. This is not a Linux devicetree. It is 69 The platform version is only for informing platform firmware about 70 what kind of ``sbsa-ref`` board it is running on. It is neither 74 The ``machine-version-major`` value is updated when changes breaking 76 is updated when features are added that don't break fw compatibility. 84 GIC information is present in devicetree. 87 GIC ITS information is present in devicetree. [all …]
|
/qemu/docs/devel/ |
H A D | control-flow-integrity.rst | 12 CFI is a hardening technique that focusing on guaranteeing that indirect 21 As of now, the only compiler that provides support for CFI is Clang. 35 To build with CFI, the minimum requirement is Clang 6+. If you 40 The easies way of doing this is by selecting the AR provided by LLVM:: 44 CFI is enabled on every binary produced. 47 of a CFI violation is offered (``--enable-debug-cfi``). 76 3. Plugins, since a plugin is implemented as an external library 87 If you are working on function that is performing a call using an 107 when the function call is performed. 121 fuzzing, that is to make sure that CFI is not triggering any false positive [all …]
|
H A D | memory.rst | 88 It is valid to add subregions to a region which is not a pure container 95 the whole address range; this is often clearer and is preferred. 185 owner is leaked. 188 There is an exception to the above rule: it is okay to call 197 this exception is rarely necessary, and therefore it is discouraged, 198 but nevertheless it is used in a few places. 201 machine object is actually used as the owner. Since instance_finalize is 228 B and C. B is a container mapped at 0x2000, size 0x4000, priority 2; C is 277 - if the subregion is a container, the same algorithm is used within the 279 - if the subregion is an alias, the search is continued at the alias target [all …]
|
H A D | reset.rst | 39 This is called for a reset which is being done to put the system into a 70 error is not likely to happen. 96 of an object is split into three well defined phases. 119 (if an object is already in reset state when calling 226 object is in reset. The state is changed after the *exit* is propagated to 237 true is if an external interaction (like changing an io) is made during 258 ``get_state()`` is simple. *resettable* is an interface and, as a consequence, 290 *exit* phase is an error. 295 There is currently 2 cases where this function is used: 307 flow is: [all …]
|
H A D | decodetree.rst | 5 A *decodetree* is built from instruction *patterns*. A pattern may 7 on what is convenient for further processing. 10 describes the condition under which the pattern is matched:: 32 of the field and the second number is the length of the field. If the 's' is 33 present, the field is considered signed. 54 If ``!function`` is specified, the concatenated result is passed through the 61 A field with no ``fields`` and no ``!function`` is in error. 93 identifier is the argument name and the second identifier is 94 the argument type. If the colon is missing, the argument 100 If ``!extern`` is specified, the backing structure is assumed [all …]
|
H A D | rcu.txt | 4 Read-copy update (RCU) is a synchronization mechanism that is used to 5 protect read-mostly data structures. RCU is very efficient and scalable 6 on the read side (it is wait-free), and thus can make the read paths 14 lock" (BQL). Also, restricting updates to a single task is done in 25 the updater. This is the reason why RCU is more scalable than, 31 How is this possible? The basic idea is to split updates in two phases, 40 Here is a picture: 63 The core RCU API is small: 83 synchronize_rcu is running. Because of this, it is better that 163 data item that is already accessible to readers. This is the [all …]
|
H A D | lockcnt.txt | 6 callbacks like this is not safe: 53 general is complementary: 63 - reference counting is often applied to code that is not thread-safe 71 With reference counting, reclamation is deterministic. 88 counter is zero and the mutex is taken. 91 mutex is taken. 143 incrementing the counter while it is non-zero); 149 the data structure is expected to be rare. 154 zero and the mutex is taken---even if the mutex is taken by a write, 159 - concurrent access is possible but rare [all …]
|
H A D | docs.rst | 6 QEMU's documentation is written in reStructuredText format and 14 (HMP) commands is written in files with the ``.hx`` suffix. These 22 The syntax of these ``.hx`` files is simple. It is broadly an 27 ``HXCOMM`` is the comment marker. The line, including any arbitrary 37 the ``.hx`` extension, and ``LABEL`` is the text provided within the 46 be in the C code block. If there is a string inside the brackets, 47 this is the heading to use. If this string is empty, it produces 48 a blank line in the ``--help`` output and is ignored for the rST 51 ``ARCHHEADING()`` is a variant of ``DEFHEADING()`` which produces 56 of the file to see what the expected usage is, because this [all …]
|
/qemu/tests/multiboot/ |
H A D | modules.out | 13 Content: 'This is a test file that is used as a multiboot module.' 20 Content: 'This is a test file that is used as a multiboot module.' 27 Content: 'This is a test file that is used as a multiboot module.' 34 Content: 'This is a test file that is used as a multiboot module.' 36 Content: 'This is a test file that is used as a multiboot module.' 38 Content: 'This is a test file that is used as a multiboot module.'
|
/qemu/docs/interop/ |
H A D | qcow2.txt | 25 is stored (NB: The string is not null terminated). 0 if the 150 It is an error if this bit is set without the 206 *. A field is considered not present when header_length is less than or equal 234 additional field is not aligned, some padding is needed. This padding must be 277 length is the string length and the string is not '\0' terminated. (The header 279 neither is padding always necessary nor is there a guarantee that zero bytes 440 that it is used, and >= 2 means that it is used and any write access must 563 nor is data read from the backing file if the cluster is 781 This flags is meaningful when the extra data is 856 a cluster boundary. If the offset is 0, the cluster is [all …]
|
H A D | pr-helper.rst | 25 All data transmitted on the socket is big-endian. 35 is closed. On the other hand, it is acceptable for a bit to be 0 in 39 Right now no feature is defined, so the two parties always write four 45 It is invalid to send multiple commands concurrently on the same 46 socket. It is however possible to connect multiple sockets to the 61 for PERSISTENT RESERVE OUT) is limited to 8 KiB. 64 CDB. The length of the parameter list is taken from the CDB itself. 71 and only if the SCSI status is 0x00, i.e. GOOD) 75 - if the size is nonzero, the payload follows 78 it is only valid if the SCSI status is CHECK CONDITION (0x02). [all …]
|
H A D | vhost-user.rst | 124 back-end will process. This is a free-running index that is not 140 back-end will process. This is a free-running index that is not 708 operation is completed if the reply-ack feature is negotiated and 1259 invalid FD flag. This flag is set when there is no file descriptor 1278 invalid FD flag. This flag is set when there is no file descriptor 1297 invalid FD flag. This flag is set when there is no file descriptor 1415 When ``VHOST_USER_PROTOCOL_F_CONFIG`` is negotiated, this message is 1429 When ``VHOST_USER_PROTOCOL_F_CONFIG`` is negotiated, this message is 1498 The value returned is an error indication; 0 is success. 1591 Exactly one file descriptor from which the memory is mapped is [all …]
|
/qemu/docs/specs/ |
H A D | ivshmem-spec.rst | 54 it is configured for interrupts. 87 is received. Reading the register clears it. 90 this is zero. Else, it is the device's ID (between 0 and 65535). 95 There is no good way for software to find out whether the device is 103 If the device is not configured for interrupts, the write is ignored. 106 device is not capable to tell guest software whether setup is 110 interrupt vectors connected, the write is ignored. The device is not 116 operation is therefore impossible. 164 is not capable to tell guest software whether the server is still up. 185 only when the character device is destroyed. [all …]
|
H A D | ppc-spapr-numa.rst | 49 The ibm,associativity-reference-points property is an array that is used 134 is 10. 148 The result is that each OS is free to implement and to interpret the distance 165 topology of the guest. The overall design is: 193 This is how it is being done: 300 node 1 to 2 is 80, matching at 0x1, and distance from 1 to 3 is 40, 310 between 2 and 3 is 20, i.e. a match in 0x3: 330 0 and 3 is 40, we calculated it as 20. This is what the current logic and 361 kind of topology where the distance from a node A to B is X, B to C is X, but 362 the distance A to C is not X. E.g.: [all …]
|
/qemu/docs/tools/ |
H A D | qemu-img.rst | 48 *FMT* is the disk image format. It is guessed automatically in most 63 *SNAPSHOT_PARAM* is param used for internal snapshot, format is 76 object type is a ``secret``, which is used to supply passwords and/or 288 If *FLUSH_INTERVAL* is specified for a write test, the request queue is 297 If ``-n`` is specified, the native AIO backend is used if possible. On 430 compression is read-only. It means that if a compressed sector is 556 This is shown as ``no`` if the image is dirty and will have to be 618 In JSON format, the ``offset`` field is optional; it is absent in 620 If ``data`` is false and the ``offset`` field is present, the 815 If this option is set to ``on``, the image is encrypted with [all …]
|
/qemu/docs/system/s390x/ |
H A D | vfio-ap.rst | 51 An AP queue is the means by which an AP command-request message is sent to an 84 an APID from 0-255. If a bit is set, the corresponding adapter is valid for 103 APQN is defined by the matrix calculated from the APM and AQM; it is the 230 0-255. If a bit is set, the APID is marked as usable only by the default AP 237 0-255. If a bit is set, the APQI is marked as usable only by the default AP 263 the mask. If the given string is shorter than the mask, it is padded 517 are installed on the host system. The feature is s390-specific and is 687 vfio_ap module is: 824 This is how the matrix is configured for Guest1:: 851 This is how the matrix is configured for Guest2:: [all …]
|
/qemu/docs/devel/migration/ |
H A D | vfio.rst | 6 the guest is running on source host and restoring this saved state on the 8 devices is done in QEMU. 19 When pre-copy is supported, it's possible to further reduce downtime by 62 active only when the VFIO device is in pre-copy states. 113 In this method dirty tracking is done by IOMMU. However, there is currently no 133 System memory dirty pages tracking when vIOMMU is enabled 169 Data of VFIO device for pre-copy phase is copied 176 Then the VFIO device is put in _STOP_COPY state 180 pending data is 0 185 .save_cleanup() is called [all …]
|
/qemu/qapi/ |
H A D | misc-target.json | 27 # @uninit: The guest is uninitialized. 33 # data is being imported. 55 # @enabled: true if SEV is active 146 # SEV is enabled 161 # This command is used to get the SEV capabilities, and is supported 212 # This command is used to get the SEV attestation report, and is 258 # program is running upon. 316 # @sgx: true if SGX is supported 322 # @flc: true if FLC is supported 380 # @closed: The port is unused. [all …]
|
/qemu/docs/system/i386/ |
H A D | amd-memory-encryption.rst | 4 Secure Encrypted Virtualization (SEV) is a feature found on AMD processors. 6 SEV is an extension to the AMD-V architecture which supports running encrypted 9 unencrypted version. Each encrypted VM is associated with a unique encryption 10 key; if its data is accessed by a different entity using a different key the 131 The launch measurement is calculated as: 144 The value of GCTX.LD is 152 * if kernel is used, and ``kernel-hashes=on``, then ``kernel_hashes_blob`` is 156 * if SEV-ES is enabled (``policy & 0x4 != 0``), ``vmsas_blob`` is the 204 * SME is section 7.10 205 * SEV is section 15.34 [all …]
|
/qemu/docs/system/ |
H A D | qemu-block-drivers.rst.inc | 73 If this is set to ``aes``, the image is encrypted with 128-bit AES-CBC. 169 Note: this option is only valid to new or empty files. If there is 172 filename`` to check if the NOCOW flag is set or not (Capital 'C' is 297 If this option is set to ``on``, the image is created with metadata 444 alternate syntax ``\\.\d:`` is supported. ``/dev/cdrom`` is 453 where *N* is the drive number (0 is the first hard disk). 705 *PORT* is the port number on which glusterd is listening. This is optional 721 default is stderr. 771 username is tried. 777 *PORT* is the port number on which sshd is listening. By default [all …]
|
/qemu/docs/ |
H A D | rdma.txt | 59 use of RDMA is discouraged and it is recommended to use standard TCP migration. 138 Migration with RDMA is separated into two parts: 143 "Everything else" is transmitted using a formal 163 basically done. All that is required is for the sender 201 The maximum number of repeats is hard-coded to 4096. This is a conservative 281 written if chunk registration is disabled. This is accomplished using 288 Current version of the protocol is version #1. 291 negotiation. (i.e. There is only one version number that is referred to 303 There is no data portion of this header right now, so there is 315 If the version is invalid, we throw an error. [all …]
|
H A D | qcow2-cache.txt | 6 This work is licensed under the terms of the GNU GPL, version 2 or 12 performance significantly. However, setting the right cache sizes is 24 A qcow2 file is organized in units of constant size called clusters. 26 The cluster size is configurable, but it must be a power of two and 42 There is one single L1 table per disk image. The table is small and is 83 caches (in bytes) is: 101 image size (given that the default cluster size is used): 106 cluster size of 64 KB, it is 256 KB (262144 bytes). This is sufficient for 138 - The default (and minimum) refcount cache size is 4 clusters. 163 and is kept in the cache. If the cache is full then a complete table [all …]
|