/qemu/scripts/performance/ |
H A D | topN_perf.py | 113 functions = [] variable 117 functions = [line for line in data.readlines() if line and line[0] variable 121 number_of_top_functions = top if len(functions) > top else len(functions) 124 top_functions = functions[:number_of_top_functions]
|
/qemu/docs/devel/ |
H A D | loads-stores.rst | 9 QEMU internally has multiple families of functions for performing 19 These functions operate on a host pointer, and should be used 53 There are also functions which take the size as an argument: 76 These functions operate on a guest virtual address, plus a context 87 These functions may cause a guest CPU exception to be taken 101 it in other functions that are *not* the top level 104 if needed to the functions that the helper calls. 131 These functions work like the ``cpu_{ld,st}_mmu`` functions except 164 These functions work like the ``cpu_{ld,st}_mmuidx_ra`` functions 169 virtual address from helper functions, unless the access should [all …]
|
H A D | reset.rst | 21 to control it. All resettable control functions must be called while holding 27 ``resettable_reset()``. These functions take two parameters: a pointer to the 73 possible to interleave multiple calls to these three functions. There may 89 calls to resettable interface are done through base class functions, such an 92 For Devices and Buses, the following helper functions exist: 99 prefer to use these functions instead of ``resettable_reset()``. 101 Device and bus functions co-exist because there can be semantic differences 156 must provide and what functions it has access to. It is intended for people 351 It also calls all the functions registered with it using 352 ``qemu_register_reset()``. Those functions are called during the
|
H A D | bitops.rst | 5 The header ``qemu/bitops.h`` provides utility functions for
|
H A D | block-coroutine-wrapper.rst | 5 A lot of functions in QEMU block layer (see ``block/*``) can only be 6 called in coroutine context. Such functions are normally marked by the
|
H A D | style.rst | 137 Wrapped version of standard library or GLib functions use a ``qemu_`` 139 example ``qemu_strtol`` or ``qemu_mutex_lock``. Other utility functions 141 prefix, for example ``pstrcpy`` or bit manipulation functions such as 144 The ``qemu_`` prefix is also used for functions that modify global 149 Public functions from a file or subsystem (declared in headers) tend 151 ``tlb_`` for functions from ``cputlb.c`` or ``cpu_`` for functions 198 Rationale: a consistent (except for functions...) bracing style reduces 314 instantiate multiple similar functions. While such abuse of the macro 466 fall-back to a smaller one if need be we should use functions like 516 QEMU provides other useful string functions: [all …]
|
H A D | rust.rst | 187 Generally speaking, these are all removed in the corresponding Rust functions: 289 a raw pointer, for use in calls to C functions. It can be used for 321 functions. Put them in a trait and access it through generic parameters. 325 **Prefer unsafe traits to unsafe functions** 326 Unsafe traits are much easier to prove correct than unsafe functions. 328 by generic functions. C code usually places metadata in global variables; 353 By conventions, procedural macros are split in two functions, one 369 The ``qemu_api_macros`` crate has utility functions to examine a 371 with named fields). These functions return ``Result<..., MacroError>``
|
H A D | multiple-iothreads.rst | 77 Instead, use the ``AioContext`` functions directly (see ``include/block/aio.h``): 102 ``AioContext`` functions like ``aio_set_fd_handler()``, 135 the ``BlockDriverState``'s ``AioContext``. The functions
|
H A D | replay.rst | 12 Record/replay functions are used for the deterministic replay of qemu 38 * wrappers for clock and time functions to save their return values in the log 110 Two functions are used for this purpose; because these actions change 162 bdrv coroutine functions at the top of block drivers stack. 174 ``replay_bh_schedule_event`` or ``replay_bh_schedule_oneshot_event`` functions. 212 is not defined. It means that you should not call functions like
|
H A D | qom.rst | 42 // No new virtual functions: we can reuse the typedef for the 142 its virtual functions. Here is how the above example might be modified 314 which do not require any virtual functions in the class, the 345 If the type requires virtual functions to be declared in the class 352 own virtual functions (i.e. which was declared with OBJECT_DECLARE_SIMPLE_TYPE)
|
/qemu/scripts/coccinelle/ |
H A D | errp-guard.cocci | 32 // Disable optional_qualifier to skip functions with 35 // Skip functions with "assert(_errp && *_errp)" statement, because 61 // Add invocation of ERRP_GUARD() to errp-functions where // necessary 103 // functions to warn (even those we are not going to convert). 166 // Match functions with propagation of local error to errp. 167 // We want to refer these functions in several following rules, but I 169 // (to not match another functions with same name in following rules). 170 // Not-proper way is as follows: rename errp parameter in functions 234 // Note also that errp-cleaning functions 263 // Convert error clearing functions
|
H A D | inplace-byteswaps.cocci | 1 // Replace uses of in-place byteswapping functions with calls to the 2 // equivalent not-in-place functions. This is necessary to avoid
|
/qemu/docs/ |
H A D | pcie_sriov.txt | 8 virtual functions (VFs) for the main purpose of eliminating software 37 supports functions beyond it's "own" function space (0-7), 38 which is necessary to support more than 7 functions, or 39 if functions extends beyond offset 7 because they are placed at an 70 which will delete all the virtual functions and associated resources.
|
/qemu/docs/sphinx/ |
H A D | kerneldoc.py | 93 functions = self.options.get('functions').split() 94 if functions: 95 for f in functions:
|
/qemu/scripts/ci/ |
H A D | gitlab-ci-section | 5 # functions section_start and section_end which will emit marker lines 11 # a CI config; the section_start and section_end functions will
|
/qemu/docs/devel/migration/ |
H A D | main.rst | 173 functions. The first one will generate a device ``instance_id`` 208 Each device has to register two functions, one to save the state and 219 Two functions in the ``ops`` structure are the ``save_state`` 220 and ``load_state`` functions. Notice that ``load_state`` receives a version_id 250 or not. If this functions returns false, the subsection is not sent. 269 The 'pre_load' and 'post_load' functions on subsections are only 418 Massaging functions 428 The functions to do that are inside a vmstate definition, and are called: 447 Example: You can look at hpet.c, that uses the first three functions 455 If you use memory or portio_list API functions that update memory layout outside [all …]
|
H A D | qatzip-compression.rst | 97 ``QAT`` supports physical functions(PFs) and virtual functions(VFs) for
|
/qemu/docs/system/ |
H A D | sriov.rst | 8 multiple virtual functions (VFs) for the main purpose of eliminating software 16 virtio-net-pci functions to a bus. Below is a command line example:
|
/qemu/include/exec/ |
H A D | helper-proto.h.inc | 3 * Helper file for declaring TCG helper functions. 4 * This one expands prototypes for the helper functions.
|
H A D | helper-gen.h.inc | 3 * Helper file for declaring TCG helper functions. 4 * This one expands generation functions for tcg opcodes.
|
/qemu/target/hexagon/ |
H A D | README | 55 Qemu helper functions have 3 parts 135 address to helper functions. Here's an example for an HVX vector-add-word 160 functions from tcg-op-gvec.h. Here's the override for this instruction. 184 these functions record the reads and writes to registers by calling ctx_log_*. 223 The functions in this file generate TCG code for a translation block. Some 224 important functions in this file are
|
/qemu/scripts/oss-fuzz/ |
H A D | instrumentation-filter-template | 14 # Enable instrumentation for all functions in those files
|
/qemu/hw/pci/ |
H A D | meson.build | 14 # The functions in these modules can be used by devices too. Since we
|
/qemu/docs/specs/ |
H A D | acpi_nvdimm.rst | 18 functions specific to a particular NVDIMM implementation. 42 control functions that are consumed by the device driver. 174 QEMU internal use only _DSM functions
|
/qemu/tests/docker/dockerfiles/ |
H A D | debian-bootstrap.docker | 13 RUN sed -i 's/in_target mount/echo not for docker in_target mount/g' /debootstrap/functions
|