Home
last modified time | relevance | path

Searched refs:use (Results 151 – 175 of 386) sorted by relevance

12345678910>>...16

/qemu/docs/devel/
H A Drcu.txt10 thus it is not used alone. Typically, the write-side will use a lock to
86 the updater is protected by the BQL), you can use call_rcu.
118 struct, you can use the following macro.
147 RCU read-side critical sections must use qatomic_rcu_read() to
307 use call_rcu() instead:
337 foo_unref could use a mechanism such as bottom halves to move deallocation
H A Dmemory.rst84 The typical use is to track parts of the address space which will be
138 only used for debugging purposes, but RAM regions also use the name to identify
148 the guest, or as long as the region is in use by a virtual CPU or another
169 You must not destroy a memory region as long as it may be in use by a
216 you can use memory_region_add_subregion_overlap() both to specify a region
258 a bus or a memory controller) can use them to manage the interaction of
349 rather than completing successfully; those devices can use the
H A Dmulti-process.rst19 potentially use the hypervisor's access privileges to access data it is
48 this service would not be able to use this exploit to access files or
304 The proxy object model will use device proxy objects to replace the
387 be injected into the guest. For example, a PCI device object may use
481 them, but must use ``memory_region_init_ram_from_fd()`` instead of
499 The device emulation objects will use ``memory_region_init_io()`` to
503 In order to use ``address_space_rw()`` in the emulation process to
550 When an IOMMU is in use in QEMU, DMA translation uses IOMMU memory
661 acknowledged. The main use of the second queue is to validate MMIO
807 VM. KVM will use the MMIO's guest physical address to search for a
[all …]
H A Dreplay.rst52 QEMU should work in icount mode to use record/replay feature. icount was
54 of the virtual machine. We also use icount to control the occurrence of the
93 To preserve this order we use checkpoints. When a specific clock is processed
147 All virtual devices should use virtual clock for timers that change the guest
151 Virtual devices can also use realtime clock for the events that do not change
153 speed, use virtual clock with EXTERNAL attribute. It is not deterministic,
H A Dfuzzing.rst6 how to use it to implement additional fuzzers.
25 such as out-of-bounds accesses, use-after-frees, double-frees etc.::
94 can use Clang coverage:
156 virtio-net example, we could use one of ::
172 To ensure that these env variables have been configured correctly, we can use::
H A Dtcg-plugins.rst36 behaviour. In this case the howvec plugin is being asked to use inline
99 can miss counts. If you want absolute precision you should use a
345 If your program is single-threaded you can use the ``inline`` option for
456 asynchronous events are introduced. While the use of -icount can
490 By default the plugin tracks both reads and writes. You can use one
550 registers with multiple ``reg`` options. You can also use glob style matching if you wish::
560 instructions. You can use the ifilter to catch these cases:
619 :code:`fifo`, and :code:`rand`. The plugin will use the specified policy for
H A Dsubmitting-a-pull-request.rst19 do this is to use ``git format-patch --cover-letter`` to create the
36 make sure you've copied their signoffs across. (If you use the `patches
/qemu/
H A D.gitlab-ci.yml9 # To use a different set of jobs than the mainstream QEMU project,
/qemu/qapi/
H A Dblock.json17 # Policy that BIOS should use to interpret cylinder/head/sector
19 # translate logical CHS to physical; instead, they will use logical
/qemu/gdbstub/
H A Dmeson.build3 # types. The bits pushed to system/user.c try to use guest agnostic
/qemu/docs/
H A Dthrottle.txt16 This document explains how to use the throttling code in QEMU, and how
83 this section we'll use 'iops-total' as an example.
267 Different filters can use the same group so the limits are shared as
296 enables use of 'limits'.
298 Once we have a throttle-group we can use the throttle block filter,
343 Now we can define the drives, and for each one of them we use two
H A Dqdev-device-use.txt24 bus named pci.0. To put a FOO device into its slot 4, use -device
53 to use, and the drive's address on that bus. Details depend on TYPE.
110 1. You can use -nodefaults to suppress the default unit 0, see
184 have to use something like
233 user,guestfwd=... You can use chardev:CHR-ID in place of
256 you have to use usb-net.
/qemu/docs/specs/
H A Divshmem-spec.rst11 The device can use a shared memory object on the host directly, or it
35 There are two ways to use this device:
38 you have access to the shared memory in the guest and can use it as
167 production. It assumes all clients use the same number of interrupt
/qemu/docs/user/
H A Dmain.rst38 correctly. x86 and Arm use a global lock in order to preserve their
87 Activate logging of the specified items (use '-d help' for a list of
234 Activate logging of the specified items (use '-d help' for a list of
/qemu/python/
H A DREADME.rst29 and are not needed to simply use these libraries.
50 2. Inside a Python script, use ``sys.path`` to forcibly include a search
/qemu/docs/system/devices/
H A Dvhost-user.rst19 platform details for what sort of virtio bus to use.
69 expert use while developing new backends. The user needs to specify
H A Dvhost-user-rng.rst31 use to communicate as well as share the guests memory over a memfd.
/qemu/docs/system/arm/
H A Dxscale.rst9 SL-C3200 (\"Terrier\") use a PXA270.
/qemu/hw/isa/
H A DKconfig23 # Some users of ISA_SUPERIO do not use it
/qemu/docs/system/
H A Dtarget-sparc64.rst12 The Niagara T1 emulator makes use of firmware and OS binaries supplied
/qemu/tests/vm/
H A Dcentos-8-aarch64.ks7 ignoredisk --only-use=vda
/qemu/tests/migration/aarch64/
H A Da-b-kernel.S11 # pc-relative address. Also the branch instructions should use relative
/qemu/docs/about/
H A Dindex.rst14 The second supported way to use QEMU is :ref:`User Mode Emulation`,
/qemu/plugins/
H A Dmeson.build28 # then use dlltool to assemble a delaylib.
/qemu/target/hexagon/
H A DREADME39 is a two step process. The first step is to use the C preprocessor to expand
125 In gen_tcg.h, we use the shortcode
165 Finally, we notice that the override doesn't use the TCGv_ptr variables, so
190 In addition to instruction semantics, we use a generator to create the decode
258 During the TCG generation (see translate.[ch]), we use the DisasContext to

12345678910>>...16