| /qemu/docs/devel/ |
| H A D | kconfig.rst | 11 card, even though the boards use different PCI host bridges, and they
26 to list the components they need, and the compiled executable will
52 symbols; they are only visible in the Makefile. Each configurable component
56 falsehood is written ``n``. They are defined in a Kconfig
113 if more than one default is present, they will have different
148 Subsystems always default to false (they have no ``default`` directive)
150 up to other symbols to ``select`` whatever subsystems they require.
152 They sometimes have ``select`` directives to bring in other required
166 Devices are the most complex of the five. They can have a variety
170 Devices *depend on* the bus that they lie on, for example a PCI
[all …]
|
| H A D | maintainers.rst | 7 They come from a wide range of backgrounds from unpaid hobbyists
16 They are also human and subject to the same pressures as everyone else
17 including overload and burnout. Like everyone else they are subject
45 - It has a maintainer but they don't have time to do
53 it does not mean they are paid to support you. This is open source and
76 asked by others to keep an eye on an area of code. They have generally
78 reviews, that they have a good understanding of the subsystem. They
96 GPG is used to sign pull requests so they can be identified as really
|
| H A D | code-provenance.rst | 10 patch submissions they make to the project. To put it another way,
11 contributors must indicate that they are legally permitted to contribute to
62 If the person sending the mail is not one of the patch authors, they are
73 * The non-primary author's contributions were so trivial that they can be
93 When multiple ``Signed-off-by`` tags are present, they should be strictly kept
103 mailing list, if they consider the patch acceptable, they should send an
105 review a patch should add this even if they are also adding their
110 queue it and send a pull request, they would send a mail containing a
113 maintainer wants to indicate they have done a full review they should use
117 behaviour of the patch in some manner, they should send an email reply
[all …]
|
| H A D | loads-stores.rst | 21 to guest ram or a local buffer). They deal with doing accesses
90 function call. They should therefore only be used in code that is
206 This means they must only be used from helper functions where the
275 any actions required by any tracing plugins. They are only to be
307 they perform accesses by guest virtual address, with a given ``MemOpIdx``.
309 They differ from ``cpu_{ld,st}_mmu`` in that they take the endianness
336 or device memory accesses. They take an AddressSpace, which is the
338 (They generally correspond to being the "master" end of a hardware bus
343 for the Secure world and one for NonSecure if they implement TrustZone).
348 modelling that they have an AddressSpace of their own.)
[all …]
|
| H A D | multiple-iothreads.rst | 18 same event loop, which monitors their file descriptors until they become
26 not shared completely. Sometimes it is useful to remember that although they
27 are conceptually similar they are currently not interchangeable.
73 Since they implicitly work on the main loop they cannot be used in code that
74 runs in an ``IOThread``. They might cause a crash or deadlock if called from an
104 are thread-safe. They can be used to trigger activity in an ``IOThread``.
|
| H A D | tcg-plugins.rst | 22 your plugin upstream so they can be updated if/when the API changes.
25 version they were built against. This can be done simply by::
55 if they want to dump a summary of collected information once the
62 callbacks to some or all instructions when they are executed.
159 plugin callbacks). This allows plugins to remove themselves if they no
|
| H A D | submitting-a-patch.rst | 29 preserve CCs and keep non-subscribers in the loop on the threads they
92 unrelated to the bug they're chasing.) Put documentation first, not
166 for fixing this bug" (they can go below the ``---`` line in the email so
167 they don't go into the final commit message). Make sure the body of the
306 Send patches inline so they are easy to reply to with review comments.
328 Patches are easier to find if they start a new top-level thread, rather
364 When reviewers don't know your goal at the start of their review, they
366 series, because they do not have enough context yet at that point of
372 entire series; potential reviewers know what files they are interested
373 in, and they need an easy way determine if your series touches them.
[all …]
|
| H A D | stable-process.rst | 54 notify them), they will add the same line to the patch, meaning that
66 When the stable maintainers prepare a new stable release, they will prepare
69 please verify that they look fine, especially if the maintainer had to tweak
|
| H A D | multi-thread-tcg.rst | 130 now invalid blocks need the jump patches reversing so they will return
247 Updates to interrupt state are also protected by the BQL as they can
263 of view of external observers (e.g. another processor core). They can
268 on the various forms of memory barrier and the guarantees they can
272 provide explicit memory ordering semantics. However they can be used
341 because they are within the context of a single translation block so
357 Arm's ldrex/strex instructions. While they are susceptible to the ABA
|
| H A D | memory.rst | 130 are for special cases only, and so they do not automatically
157 ioeventfd) can be changed during the region lifecycle. They take effect
194 QEMU building the guest's memory map; they are never accessed directly.
203 on regions that have no owner, unless they are aliases or containers.
246 even where they overlap with C. In ranges where B has not mapped anything
256 regions are only compared when they are both children of the same container.
261 they do not overlap each other. It is the relative priority of B and C
|
| H A D | trivial-patches.rst | 10 on the mailing list even though they require only a small amount of
43 A single team member can be on duty as long as they like. The suggested
|
| H A D | reset.rst | 43 have some non-deterministic state they want to reinitialize to a different
44 value on each cold reset, such as RNG seed information, and which they
97 These are simple wrappers around resettable_reset() function; they only cast the
140 ``resettable_assert_reset()`` or ``resettable_reset()``, they are not
164 phase of the reset; they are name ``phases.enter()``, ``phases.hold()`` and
165 ``phases.exit()``. They all take the object as parameter. The *enter* method
|
| /qemu/docs/system/ |
| H A D | images.rst | 31 read only. When sectors in written, they are written in a temporary file
74 you can always make VM snapshots, but they are deleted as soon as you
79 - They cannot cope with removable devices if they are removed or
|
| H A D | security.rst | 26 The following entities are untrusted, meaning that they may be buggy or
35 Bugs affecting these entities are evaluated on whether they can cause damage in
109 launch QEMU, such as libvirt. They are also platform-specific so they are only
122 traditional UNIX process and file permissions model. They restrict the QEMU
|
| H A D | target-riscv.rst | 15 then built into machines which can vary still further even if they use
86 do is specify the kernel they want to boot with the ``-kernel`` option
91 the images they need.
|
| /qemu/include/block/ |
| H A D | block-global-state.h | 40 * necessarily limited to running under the BQL, but they would
44 * moment, so they have been placed in the GS API (for now).
51 * to catch when they are accidentally called without the BQL.
303 * that they can prepare IOMMU mapping etc., to get better performance.
305 * Buffers must not overlap and they must be unregistered with the same <host,
306 * size> values that they were registered with.
|
| /qemu/docs/interop/ |
| H A D | qmp-spec.rst | 41 be in a certain order. However, in real protocol usage they can be in
130 the server reads and queues commands as they arrive. It executes
207 response. They are called "asynchronous events".
344 advertised in the `Server Greeting`_ which they support.
357 that array and enable the capabilities they support.
364 errors occur, they will be reported before the command generated any
381 this, a Client should be "conservative in what they send, and liberal in
382 what they accept".
|
| /qemu/docs/devel/migration/ |
| H A D | compatibility.rst | 8 target. There are two cases, they are the same version or they are
9 different versions. The easy case is when they are the same version.
10 The difficult one is when they are different versions.
12 There are two things that are different, but they have very similar
60 It needs to use the definition of pc-5.1 and the devices as they
169 they are the same.
249 See when they talk about migration they recommend that one chooses the
308 Other devices have worse control about individual features. If they
|
| /qemu/docs/devel/testing/ |
| H A D | acpi-bits.rst | 75 test failures. This is the script one would be interested in if they wanted
78 modify this script unless they wanted to enhance or change the log parsing
147 (a) They are python2.7 based scripts and not python 3 scripts.
148 (b) They are run from within the bios bits VM and is not subjected to QEMU
150 (c) They need not be loaded by the test framework by accident when running
|
| /qemu/tests/tcg/minilib/ |
| H A D | Makefile.target | 4 # The system tests are very constrained in terms of the library they
8 # They assume each arch has provided a putc function.
|
| /qemu/python/ |
| H A D | README.rst | 13 environment. If you are inside a virtual environment, they will
28 packages for testing this package. They are not runtime requirements,
54 A strong downside to both approaches is that they generally interfere
|
| /qemu/linux-user/sparc/ |
| H A D | target_syscall.h | 31 * SPARC kernels don't define this in their Kconfig, but they have the
32 * same ABI as if they did, implemented by sparc-specific code which fishes
|
| /qemu/target/arm/tcg/ |
| H A D | translate-neon.c | 124 /* UNDEF accesses to D16-D31 if they don't exist. */ in do_neon_ddda()
154 /* UNDEF accesses to D16-D31 if they don't exist. */ in do_neon_ddda_env()
186 /* UNDEF accesses to D16-D31 if they don't exist. */ in do_neon_ddda_fpst()
242 /* UNDEF accesses to D16-D31 if they don't exist. */ in trans_VCADD()
312 /* UNDEF accesses to D16-D31 if they don't exist. */ in trans_VFML()
406 /* UNDEF accesses to D16-D31 if they don't exist. */ in trans_VFML_scalar()
480 /* UNDEF accesses to D16-D31 if they don't exist */ in trans_VLDST_multiple()
582 /* UNDEF accesses to D16-D31 if they don't exist */ in trans_VLD_all_lanes()
674 /* UNDEF accesses to D16-D31 if they don't exist */ in trans_VLDST_single()
791 /* UNDEF accesses to D16-D31 if they don't exist. */ in do_3same()
[all …]
|
| /qemu/scripts/coccinelle/ |
| H A D | qobject.cocci | 1 // Use QDict macros where they make sense
28 // Use QList macros where they make sense
|
| /qemu/linux-user/aarch64/ |
| H A D | vdso.S | 61 * because they cause libgcc to crash, but that's because they're wrong.
|