/qemu/docs/devel/ |
H A D | blkverify.txt | 19 The blkverify protocol has two child block devices, the "test" device and the 23 The "raw" device is a raw image, a flat file, that has identical starting 34 Imagine raw.img has 0xcd repeated throughout its first sector:
|
H A D | multi-thread-tcg.rst | 12 system-mode emulation. user-mode emulation has always mirrored the 30 guest has had the required work done to support this safely 98 Each vCPU has its own TCG context and associated TCG region, thereby 265 The Linux kernel has an excellent `write-up 285 fairly strong guarantees of sequential consistency whereas Arm has 299 The system currently has a tcg_gen_mb() which will add memory barrier 318 are often seen when code modification has taken place to ensure the 333 guarantee that a region of memory has not been touched between the 336 successful store only if no other CPU has accessed the memory region 339 Traditionally TCG has generated a series of operations that work
|
H A D | atomics.rst | 48 either side of it to the other side. The compiler barrier has no direct 209 Note that the first load really has to have a _data_ dependency and not 221 mostly used when a data structure has one thread that is always a writer 298 either *acquire* or *release* semantics [#rmw]_. This has two effects: 316 - ``pthread_mutex_lock`` has acquire semantics, ``pthread_mutex_unlock`` has 321 ``pthread_cond_wait`` has both release semantics (synchronizing with 325 - ``pthread_create`` has release semantics and synchronizes with the start 326 of the new thread; ``pthread_join`` has acquire semantics and synchronizes 329 - ``qemu_event_set`` has release semantics, ``qemu_event_wait`` has 399 Finally, this more complex example has more than two accesses and data
|
H A D | decodetree.rst | 9 Each pattern has both *fixedbits* and *fixedmask*, the combination of which 47 cannot currently do both at once (i.e. pattern P uses format F; F has 49 has a field C that refers to a named field D that is defined in F). 179 come in handy when fields overlap between patterns and one has to 233 When the *cf* field is zero, the instruction has no side effects, 235 is discarded and so the instruction has no effect. When the *rt2*
|
H A D | zoned-storage.rst | 20 - BLK_Z_NONE: The non-zoned model has no zones support. It includes both 26 block layer while processing I/O requests. A BlockBackend has a root pointer to 55 Additionally, QEMU has several ways of supporting zoned storage, including:
|
H A D | reset.rst | 105 local state of the object; it must not do anything that has a side-effect 110 group which is being reset has had its *enter* phase executed. At this point 123 the object does not need to care how many of reset controllers it has and how 131 must provide and what functions it has access to. It is intended for people 132 who want to implement or convert a class which has the resettable interface; 229 This function may be used if the object behavior has to be adapted 230 while in reset state. For example if a device has an irq input, 319 the current machine, if it has one. That method must call 320 ``qemu_devices_reset()``. If the machine has no reset method,
|
/qemu/docs/system/arm/ |
H A D | nuvoton.rst | 8 Hyperscale applications. The former is a superset of the latter, so NPCM750 has 13 The NPCM750 SoC has two Cortex-A9 cores and is targeted for the Enterprise 18 The NPCM730 SoC has two Cortex-A9 cores and is targeted for Data Center and
|
/qemu/ |
H A D | .patchew.yml | 3 # Patchew configuration in case patchew.org disappears or has to be 156 # HEAD pointing to a commit that has the patches applied on top of "base" 185 # HEAD pointing to a commit that has the patches applied on top of "base" 214 # HEAD pointing to a commit that has the patches applied on top of "base" 239 # HEAD pointing to a commit that has the patches applied on top of "base"
|
/qemu/docs/about/ |
H A D | deprecated.rst | 210 The ``dtb-kaslr-seed`` property on the ``virt`` board has been 225 The machine is no longer in existence and has been long unmaintained 242 the codebase, and over many years nobody has been interested in 245 has now passed away into history. We are therefore dropping support 295 has used a properly allocated identifier. Deprecate the ``use-intel-id`` 309 The 9p ``proxy`` filesystem backend driver has been deprecated and will be 327 has indicated plans for such kind of reimplementation unfortunately. 332 The 'any' CPU type was introduced back in 2018 and has been around since the 333 initial RISC-V QEMU port. Its usage has always been unclear: users don't know 337 After the introduction of the 'max' CPU type, RISC-V now has a good coverage [all …]
|
/qemu/docs/system/ |
H A D | security.rst | 14 requirements than others. The community has agreed on the overall security 70 guest has escaped the virtual machine and is able to act in the context of the 81 The principle of least privilege states that each component only has access to 83 each process only has access to resources belonging to the guest. 87 QEMU process since it already has access to those same resources from within 91 requirements. For example, guest A only has access to its own disk image file
|
/qemu/qapi/ |
H A D | job.json | 48 # @created: The job has been created, but not yet started. 66 # @pending: The job has finished its work, but has finalization steps 76 # @concluded: The job has finished all work. If auto-dismiss was set 202 # This command will refuse to operate on any job that has not yet
|
/qemu/docs/specs/ |
H A D | ppc-spapr-uv-hcalls.rst | 14 Power Architecture Reference document ([LoPAR]_). An internal ACR has been filed 33 wrapped/encrypted using the public key of a trusted system which has the private 50 response, opening a new TPM session if one has not already been opened.
|
H A D | standard-vga.rst | 41 The legacy-free variant has no ROM and has ``PCI_CLASS_DISPLAY_OTHER``
|
/qemu/docs/system/ppc/ |
H A D | pseries.rst | 169 a pSeries guest (or a PowerVM LPAR for that matter), and that is where it has 184 performance, maintenance work has been much more focused on it in the past 185 years. Maintenance for KVM-PR has been minimal. 201 This limitation has been lifted, and now it is possible to run KVM-HV inside 204 As KVM-HV has access to privileged instructions, guests that use a lot of these 205 can run much faster than with KVM-PR. On the other hand, the guest CPU has to be 287 enabled, whether or not the guest has actually entered secure mode.
|
/qemu/docs/ |
H A D | igd-assign.txt | 4 IGD has two different modes for assignment using vfio-pci: 18 theoretically has no device specific handling dependencies on vfio-pci or 45 has been assigned to a VM. It's therefore generally recommended to prevent 67 to access the reserved GTT space after reset, which it no longer has access to 121 running the IGD ROM, which has other dependencies on the device appearing
|
/qemu/tests/qapi-schema/ |
H A D | union-empty.err | 2 union-empty.json:4: union has no branches
|
H A D | bad-ident.err | 2 bad-ident.json:2: struct has an invalid name
|
H A D | reserved-command-q.err | 2 reserved-command-q.json:5: command has an invalid name
|
H A D | bad-if-keys.err | 2 bad-if-keys.json:2: 'if' condition of struct has conflicting keys
|
H A D | reserved-member-underscore.err | 2 reserved-member-underscore.json:4: 'data' member '_oops' has an invalid name
|
H A D | reserved-enum-q.err | 2 reserved-enum-q.json:4: 'data' member 'q-Unix' has an invalid name
|
H A D | reserved-member-q.err | 2 reserved-member-q.json:4: 'data' member 'q-unix' has an invalid name
|
H A D | enum-bad-name.err | 2 enum-bad-name.json:3: 'data' member 'not\possible' has an invalid name
|
H A D | alternate-base.err | 2 alternate-base.json:4: alternate has unknown key 'base'
|
H A D | features-unknown-key.err | 2 features-unknown-key.json:1: 'features' member has unknown key 'colour'
|