Home
last modified time | relevance | path

Searched refs:guest (Results 1 – 25 of 41) sorted by relevance

12

/external/valgrind/main/VEX/
DMakefile-icc22 priv/guest-generic/g_generic_x87.h \
23 priv/guest-generic/bb_to_IR.h \
24 priv/guest-x86/gdefs.h \
25 priv/guest-amd64/gdefs.h \
26 priv/guest-arm/gdefs.h \
27 priv/guest-ppc/gdefs.h \
48 priv/guest-generic/g_generic_x87.o \
49 priv/guest-generic/bb_to_IR.o \
50 priv/guest-x86/ghelpers.o \
51 priv/guest-amd64/ghelpers.o \
[all …]
DTODO.txt12 x86 guest: look at FP accuracy
/external/linux-tools-perf/Documentation/
Dperf-kvm.txt6 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>
22 a performance counter profile of guest os in realtime
27 --host and --guest are input, the perf data file name is perf.data.kvm.
28 If there is no --host but --guest, the file name is perf.data.guest.
29 If there is no --guest but --host, the file name is perf.data.host.
51 --guest=::
52 Collect guest side performance profile.
54 Guest os root file system mount directory. Users mounts guest os
[all …]
/external/qemu/docs/
DANDROID-ADB-QEMU.TXT7 For instance, connection manager in the guest system may decide to reset all
9 daemon running in the guest will be broken, and will not be reestablish until ADB
12 ADB daemon running in the guest.
29 accepting connections coming from the ADB daemon running in the guest, and
33 the host, and ADB running on the guest: ADB server receives data from ADB host,
34 and channels them through ADB client to the ADB guest. Likewise, ADB client
35 receives data from the ADB guest, and channels them through ADB server to the ADB
42 The connection between ADB host and ADB guest is considered to be established,
44 QEMUD pipe connection in the ADB client, and ADB guest is ready to receive data
48 connections are made, ADB server runs a list of pending host and guest
DANDROID-QEMU-PIPE.TXT8 _very_ fast communication channels between the guest system and the
11 From the guest, usage is simply as follows:
50 that will be accessible as /dev/qemu_pipe within the guest.
67 Each opened file descriptor to /dev/qemu_pipe in the guest corresponds to a
76 Used by the driver to indicate that the guest just opened /dev/qemu_pipe
86 Used by the driver to indicate that the guest called 'close' on the
94 Corresponds to when the guest does a write() or writev() on the
109 contained inside a single page of guest memory. This is
112 When a write() spans several pages of guest memory, the
127 Corresponds to when the guest does a read() or readv() on the
DDISPLAY-STATE.TXT146 guest event codes with functions like 'kbd_put_keycode' or 'kbd_mouse_event'.
180 consoles, or when the framebuffer's size is modified by the guest kernel.
/external/valgrind/main/lackey/tests/
Dtrue.stderr.exp12 guest instrs: ...
16 guest instrs : SB entered = ... : ...
18 IRStmts : guest instr = ... : ...
/external/chromium-trace/src/shared/css/chromeos/
Dui_account_tweaks.css7 * look and feel based on account status (owner/non-owner/guest).
10 .guest-disabled {
14 a.guest-disabled {
/external/qemu/
Dvnc-android.c273 struct VncSurface *s = &vs->guest; in vnc_update()
355 if (!vs->guest.ds) in vnc_resize()
356 vs->guest.ds = qemu_mallocz(sizeof(*vs->guest.ds)); in vnc_resize()
357 if (ds_get_bytes_per_pixel(ds) != vs->guest.ds->pf.bytes_per_pixel) in vnc_resize()
360 size_changed = ds_get_width(ds) != vs->guest.ds->width || in vnc_resize()
361 ds_get_height(ds) != vs->guest.ds->height; in vnc_resize()
362 *(vs->guest.ds) = *(ds->surface); in vnc_resize()
373 memset(vs->guest.dirty, 0xFF, sizeof(vs->guest.dirty)); in vnc_resize()
383 memset(vs->server.dirty, 0xFF, sizeof(vs->guest.dirty)); in vnc_resize()
738 guest_row = vs->guest.ds->data; in vnc_update_client()
[all …]
Dvnc.c267 struct VncSurface *s = &vs->guest; in vnc_update()
349 if (!vs->guest.ds) in vnc_resize()
350 vs->guest.ds = qemu_mallocz(sizeof(*vs->guest.ds)); in vnc_resize()
351 if (ds_get_bytes_per_pixel(ds) != vs->guest.ds->pf.bytes_per_pixel) in vnc_resize()
354 size_changed = ds_get_width(ds) != vs->guest.ds->width || in vnc_resize()
355 ds_get_height(ds) != vs->guest.ds->height; in vnc_resize()
356 *(vs->guest.ds) = *(ds->surface); in vnc_resize()
367 memset(vs->guest.dirty, 0xFF, sizeof(vs->guest.dirty)); in vnc_resize()
377 memset(vs->server.dirty, 0xFF, sizeof(vs->guest.dirty)); in vnc_resize()
732 guest_row = vs->guest.ds->data; in vnc_update_client()
[all …]
Dqemu-options.hx133 will be sent to the guest only when the data has been reported as written by
138 If your host crashes or loses power, then the guest may experience data
323 "-usbdevice name add the host or guest USB device 'name'\n")
365 "-name string set the name of the guest\n")
368 Sets the @var{name} of the guest.
477 performances, use 16 bit color depth in the guest and the host OS.
480 Standard VGA card with Bochs VBE extensions. If your guest OS
486 recent XFree86/XOrg server or Windows guest with a driver for this
650 processed by the Windows guest and will re-inject them.
670 it if your guest OS complains about ACPI problems (PC target machine
[all …]
Dqemu-monitor.hx77 show guest PCMCIA status
79 show which guest mouse is receiving events
546 …"[tcp|udp]:host-port:[guest-host]:guest-port", "redirect TCP or UDP connections from host to guest…
552 Redirect TCP or UDP connections from host to guest (requires -net user).
Dvnc.h119 struct VncSurface guest; /* guest visible surface (aka ds->surface) */ member
/external/valgrind/main/docs/internals/
Dregister-uses.txt20 ebp y n & guest state
43 rbp y n & guest state
81 r31 y & guest state
191 r31 y & guest state
Dm_syswrap.txt3 to the host and then fixing up the guest state accordingly. It
Dwhy-no-libc.txt19 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
D3_2_BUGSTATUS.txt18 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
Dporting-HOWTO.txt24 - Create the Vex guest state type, VexGuest<ARCH>State
/external/wpa_supplicant_8/hostapd/
Dhostapd.vlan5 100 guest
/external/valgrind/main/gdbserver_tests/
Dmcsigpass.vgtest1 # test the signal handling, when signals are passed to the Valgrind guest.
Dmcsignopass.vgtest1 # test the signal handling, when signals are *not* passed to the Valgrind guest.
/external/valgrind/main/coregrind/
Dpub_core_transtab.h47 Addr guest; member
Dm_transtab.c675 VG_(tt_fast)[cno].guest = (Addr)key; in setFastCacheEntry()
683 vg_assert(VG_(tt_fast)[cno].guest != TRANSTAB_BOGUS_GUEST_ADDR); in setFastCacheEntry()
710 VG_(tt_fast)[j+0].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
711 VG_(tt_fast)[j+1].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
712 VG_(tt_fast)[j+2].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
713 VG_(tt_fast)[j+3].guest = TRANSTAB_BOGUS_GUEST_ADDR; in invalidateFastCache()
731 && VG_(tt_fast)[j].guest != TRANSTAB_BOGUS_GUEST_ADDR) in sanity_check_fastcache()
734 && VG_(tt_fast)[j].guest == TRANSTAB_BOGUS_GUEST_ADDR) in sanity_check_fastcache()
/external/valgrind/main/coregrind/m_gdbserver/
DREADME_DEVELOPERS40 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/qemu/distrib/
DREADME38 the guest system is idle. This is now disabled since Linux 2.6.21 and beyond use

12