Lines Matching full:functions

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
202 These functions work like the ``cpu_{ld,st}_data_ra`` functions
206 This means they must only be used from helper functions where the
207 translator has saved all necessary CPU state.  These functions are
241 These functions perform a read for instruction execution.  The ``mmuidx``
249 In general these functions should not be used directly during translation.
250 There are wrapper functions that are to be used which also take care of
274 These functions are a wrapper for ``cpu_ld*_code`` which also perform
278 There is a set of functions ending in ``_swap`` which, if the parameter
305 These functions are intended primarily to be called by the code
306 generated by the TCG backend.  Like the ``cpu_{ld,st}_mmu`` functions
335 These functions are the primary ones to use when emulating CPU
350 Functions are provided for doing byte-buffer reads and writes,
409 These are functions which are identical to
448 These are convenience functions which are identical to
508 These functions are specifically for PCI device models which need to