Searched full:precise (Results 1 – 25 of 47) sorted by relevance
12
| /qemu/tests/qemu-iotests/ |
| H A D | 243 | 60 # Can't use precise numbers here because they differ between filesystems
80 # Can't use precise numbers here because they differ between filesystems
|
| H A D | 224 | 5 # (the one of commit, to be precise)
|
| /qemu/docs/system/ |
| H A D | qemu-block-drivers.rst | 23 The HTML documentation of QEMU for more precise information and Linux
|
| H A D | qemu-cpu-models.rst | 24 The HTML documentation of QEMU for more precise information and Linux user mode emulator invocation.
|
| H A D | qemu-manpage.rst | 55 The HTML documentation of QEMU for more precise information and Linux
|
| /qemu/ |
| H A D | pythondeps.toml | 16 # precise error diagnostics to the user. For example,
|
| /qemu/tests/tcg/s390x/ |
| H A D | precise-smc-user.c | 2 * Test s390x-linux-user precise self-modifying code handling.
|
| H A D | precise-smc-softmmu.S | 2 * Test s390x-softmmu precise self-modifying code handling.
|
| H A D | Makefile.softmmu-target | 30 precise-smc-softmmu \
|
| H A D | Makefile.target | 72 Z13_TESTS+=precise-smc-user
|
| /qemu/include/exec/ |
| H A D | icount.h | 54 * (precise mode), or it is constantly approximated and corrected at
|
| /qemu/tests/qemu-iotests/tests/ |
| H A D | mirror-sparse | 101 # than expecting precise 2M and 20M images, it is better to allow for slop.
|
| /qemu/target/mips/tcg/ |
| H A D | exception.c | 122 [EXCP_C2E] = "precise coprocessor 2",
|
| /qemu/hw/display/ |
| H A D | vga_int.h | 53 struct vga_precise_retrace precise; member
|
| /qemu/docs/devel/ |
| H A D | control-flow-integrity.rst | 120 can identify such bugs in a more precise way than CFI.
|
| /qemu/accel/tcg/ |
| H A D | monitor.c | 162 * For avg host size we use the precise numbers from tb_tree_stats though. in dump_exec_info()
|
| H A D | tb-maint.c | 1051 * Without precise smc semantics, or when outside of a TB, in tb_invalidate_phys_page_unwind()
1071 * execution. We could be more precise by checking that in tb_invalidate_phys_page_unwind()
1136 * its execution. We could be more precise by checking in tb_invalidate_phys_page_range__locked()
|
| /qemu/include/standard-headers/linux/ |
| H A D | vmclock-abi.h | 34 * precise relationship of the CPU counter to real time, as calibrated by the
|
| /qemu/hw/9pfs/ |
| H A D | 9p-util.h | 30 * To be more precise: it generates a device number in glibc's format
|
| /qemu/docs/ |
| H A D | image-fuzzer.txt | 219 It should be able to perform rather complex and precise tests, that can be
|
| /qemu/include/hw/ |
| H A D | ptimer.h | 207 * precise to fractions of a nanosecond, avoiding rounding errors.
|
| /qemu/scripts/qapi/ |
| H A D | introspect.py | 69 # lack precise types for them here. Python 3.6 does not offer
|
| /qemu/include/hw/xen/interface/arch-x86/ |
| H A D | xen.h | 133 * set yet. The precise conditions are implementation specific, and
|
| /qemu/target/ppc/ |
| H A D | excp_helper.c | 574 * so always use store_next and claim we are precise in the MSR. in powerpc_excp_6xx()
715 * so always use store_next and claim we are precise in the MSR. in powerpc_excp_7xx()
865 * so always use store_next and claim we are precise in the MSR. in powerpc_excp_74xx()
1032 * so always use store_next and claim we are precise in the MSR. in powerpc_excp_booke()
1360 * so always use store_next and claim we are precise in the MSR. in powerpc_excp_books()
|
| /qemu/contrib/plugins/ |
| H A D | howvec.c | 59 * Your most precise match must be before looser matches. If no match
|
12