| /external/linux-tools-perf/src/tools/perf/Documentation/ |
| D | perf-kvm.txt | 6 perf-kvm - Tool to trace/measure kvm guest os
11 'perf kvm' [--host] [--guest] [--guestmount=<path>
14 'perf kvm' [--host] [--guest] [--guestkallsyms=<path> --guestmodules=<path>
23 a performance counter profile of guest os in realtime
28 --host and --guest are input, the perf data file name is perf.data.kvm.
29 If there is no --host but --guest, the file name is perf.data.guest.
30 If there is no --guest but --host, the file name is perf.data.host.
68 --guest=::
69 Collect guest side performance profile.
71 Guest os root file system mount directory. Users mounts guest os
[all …]
|
| D | perf-list.txt | 29 G - guest counting (in KVM guests)
69 registers: event, umask, edge, inv, cmask. Esp. guest/host only and
|
| /external/valgrind/lackey/tests/ |
| D | true.stderr.exp | 12 guest instrs: ...
16 guest instrs : SB entered = ... : ...
18 IRStmts : guest instr = ... : ...
|
| /external/valgrind/docs/internals/ |
| D | t-chaining-notes.txt | 7 check also with --vex-guest-chase-cond=yes
10 --vex-guest-max-insns=1.
62 could have held the target guest address before jumping to the stub.
156 given the address of the highest guest byte in the block so
159 The counter is placed in the first 8 bytes of the guest state,
193 The way the guest program counter is handled has changed
194 significantly. Previously, the guest PC was updated (in IR)
199 Now, each instruction must update the guest PC as its last
205 block-end transfer are both considered to write to the guest state
206 (the guest PC) and so need to be told the offset of it.
[all …]
|
| D | qemu-mips64-linux-HOWTO.txt | 9 when the guest becomes idle, qemu uses only very little host cpu, so
10 you can leave the guest idling for long periods without bad
101 (on the guest)
107 Configuring V on the guest:
|
| D | qemu-aarch64-linux-HOWTO.txt | 9 when the guest becomes idle, qemu uses only very little host cpu, so
10 you can leave the guest idling for long periods without bad
98 (on the guest)
|
| D | register-uses.txt | 20 ebp y n & guest state
43 rbp y n & guest state
81 r31 y & guest state
237 r31 y & guest state
|
| D | m_syswrap.txt | 3 to the host and then fixing up the guest state accordingly. It
|
| D | why-no-libc.txt | 19 RW> Sadly, no. Valgrind shares the address space of the guest process,
27 Valgrind tools and the guest processes do run in the same address
|
| D | 3_2_BUGSTATUS.txt | 18 n-i-bz vx1794 priv/guest-amd64/toIR.c:2512 (dis_op2_E_G): Assertion
106 150678 vx1798 priv/guest-amd64/toIR.c:3741 (dis_Grp5): Assertion
452 vx1652,3 vx1654 Vfd 132813 Assertion at priv/guest-x86/toIR.c:652 fails
|
| /external/mesa3d/src/gallium/drivers/svga/ |
| D | svga_cmd.c | 453 swc->region_relocation(swc, &cmd->guest.ptr, st->hwbuf, 0, region_flags); in SVGA3D_SurfaceDMA()
454 cmd->guest.pitch = st->base.stride; in SVGA3D_SurfaceDMA()
477 struct svga_winsys_buffer *guest, in SVGA3D_BufferDMA() argument
511 swc->region_relocation(swc, &cmd->guest.ptr, guest, 0, region_flags); in SVGA3D_BufferDMA()
512 cmd->guest.pitch = 0; in SVGA3D_BufferDMA()
|
| D | svga_resource_buffer_upload.c | 180 struct svga_winsys_buffer *guest = sbuf->hwbuf; in svga_buffer_upload_command() local
213 swc->region_relocation(swc, &cmd->guest.ptr, guest, 0, region_flags); in svga_buffer_upload_command()
214 cmd->guest.pitch = 0; in svga_buffer_upload_command()
|
| D | svga_cmd.h | 110 struct svga_winsys_buffer *guest,
|
| /external/wpa_supplicant_8/hostapd/ |
| D | hostapd.vlan | 5 100 guest
|
| /external/valgrind/gdbserver_tests/ |
| D | mcsigpass.vgtest | 1 # test the signal handling, when signals are passed to the Valgrind guest.
|
| D | mcsignopass.vgtest | 1 # test the signal handling, when signals are *not* passed to the Valgrind guest.
|
| /external/valgrind/coregrind/m_gdbserver/ |
| D | README_DEVELOPERS | 40 link it with valgrind and allow the valgrind guest process to be
43 the state of the guest.
55 stop execution of the guest to allow debugging.
65 the registers from the guest state) and writes the reply (e.g. a
68 to execute guest code. The FIFOs used to communication between
74 When a signal is to be given to the guest, valgrind core first calls
77 to the process, the signal is delivered to the guest. Otherwise, the
78 signal is ignored (not given to the guest). The user can
203 debugging the valgrind code at the same time as debugging the guest
|
| /external/valgrind/coregrind/ |
| D | pub_core_transtab.h | 48 Addr guest; member
|
| D | m_transtab.c | 1376 VG_(tt_fast)[cno].guest = key; in setFastCacheEntry()
1382 vg_assert(VG_(tt_fast)[cno].guest != TRANSTAB_BOGUS_GUEST_ADDR); in setFastCacheEntry()
1393 VG_(tt_fast)[j+0].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
1394 VG_(tt_fast)[j+1].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
1395 VG_(tt_fast)[j+2].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
1396 VG_(tt_fast)[j+3].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
|
| /external/chromium-trace/trace-viewer/third_party/webapp2/docs/tutorials/gettingstarted/ |
| D | index.rst | 6 Google App Engine. The example project, a guest book, demonstrates how to setup
|
| D | introduction.rst | 25 a simple guest book that lets users post messages to a public message board.
|
| /external/valgrind/VEX/ |
| D | TODO.txt | 12 x86 guest: look at FP accuracy
|
| /external/valgrind/ |
| D | Makefile.vex.am | 108 # a main_main.o compiled in single arch (guest==host).
110 # which is main_main.c compiled so that any guest/host combination
|
| /external/mesa3d/src/gallium/docs/source/ |
| D | distro.rst | 41 Driver for VMware virtualized guest operating system graphics processing.
|
| /external/mesa3d/src/gallium/drivers/svga/svgadump/ |
| D | svga_dump.c | 1120 _debug_printf("\t\t.guest.ptr.gmrId = %u\n", (*cmd).guest.ptr.gmrId); in dump_SVGA3dCmdSurfaceDMA()
1121 _debug_printf("\t\t.guest.ptr.offset = %u\n", (*cmd).guest.ptr.offset); in dump_SVGA3dCmdSurfaceDMA()
1122 _debug_printf("\t\t.guest.pitch = %u\n", (*cmd).guest.pitch); in dump_SVGA3dCmdSurfaceDMA()
|