/external/linux-tools-perf/ |
builtin-record.c | 393 *As for guest kernel when processing subcommand record&report, 394 *we arrange module mmap prior to guest kernel mmap and trigger 395 *a preload dso because default guest module symbols are loaded 396 *from guest kallsyms instead of /lib/modules/XXX/XXX. This 398 *in module instead of in guest kernel. 403 pr_err("Couldn't record guest kernel [%d]'s reference" 407 * We use _stext for guest kernel because guest kernel's /proc/kallsyms 417 pr_err("Couldn't record guest kernel [%d]'s reference"
|
/external/mesa3d/docs/ |
relnotes-7.7.html | 45 VMware virtual graphics device. It allows Linux OpenGL guest applications
|
contents.html | 67 <li><a href="vmware-guest.html" target="MainFrame">VMware SVGA3D guest driver</a>
|
/external/mesa3d/src/gallium/drivers/svga/include/ |
svga3d_reg.h | 42 * register. Is set by the host and read by the guest. This lets 43 * us make new guest drivers which are backwards-compatible with old 44 * SVGA hardware revisions. It does not let us support old guest 179 * and so we can send those operations to the guest. 1364 SVGA3dGuestImage guest; member in struct:__anon23313 [all...] |
/external/qemu/android/avd/ |
util.h | 67 /* Returns mode in which ADB daemon running in the guest communicates with the
|
/external/qemu/distrib/ |
README | 38 the guest system is idle. This is now disabled since Linux 2.6.21 and beyond use
|
/external/qemu/memcheck/ |
memcheck_util.c | 84 // Transfering data between guest and emulator address spaces. 92 /* Byte-by-byte copying back and forth between guest's and emulator's memory 94 * memchecker), so there is no real need to optimize it by aligning guest 96 * read / write guest's memory. */
|
memcheck_mmrange_map.h | 15 * tree (a map) of module memory mapping ranges in the guest system. The map is 17 * address range that belongs to a mapped execution module in the guest system.
|
/external/valgrind/main/VEX/priv/ |
guest_arm_defs.h | 30 /* Only to be used within the guest-arm directory. */ 62 /* Describes to the optimser which part of the guest state require 63 precise memory exceptions. This is logically part of the guest 73 /*--- arm guest helpers ---*/
|
/external/valgrind/main/VEX/pub/ |
libvex_guest_arm.h | 102 /* Used to record the unredirected guest address at the start of 110 /* Needed for Darwin (but mandated for all guest architectures): 208 /*--- Utility functions for ARM guest stuff. ---*/ 213 /* Initialise all guest ARM state. */
|
/external/valgrind/main/coregrind/m_gdbserver/ |
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/chromium/chrome/browser/chromeos/login/ |
user_controller.h | 59 // Creates a UserController representing new user or guest login. 173 // Is this the guest pod?
|
/external/chromium/chrome/browser/resources/options/ |
personal_options.js | 84 // Disable the screen lock checkbox for the guest mode. 210 * stored passwords. Password management is disabled in guest mode.
|
/external/chromium_org/chrome/browser/chromeos/login/ |
login_browsertest.cc | 147 // After a guest login, we should get the OTR default profile. 156 // Verifies the cursor is not hidden at startup when running guest session.
|
/external/chromium_org/chrome/browser/resources/chromeos/login/ |
screen_error_message.html | 92 <div id="error-guest-signin" class="error-message-paragraph guest-signin">
|
/external/chromium_org/chrome/browser/task_manager/ |
guest_resource_provider.cc | 61 return GUEST; 135 // Add all the existing guest WebContents.
|
resource_provider.h | 36 def(GUEST) /* A browser plugin guest process. */ \
|
/external/chromium_org/chrome/browser/ui/views/ |
user_manager_view.cc | 80 // Create the guest profile, if necessary, and open the user manager 81 // from the guest profile.
|
/external/chromium_org/chrome/test/telemetry/chromeos/ |
login_unittest.py | 21 self._is_guest = options.browser_type == 'cros-chrome-guest' 73 """Verifies cryptohome mount status for regular and guest user and when
|
/external/chromium_org/content/browser/browser_plugin/ |
test_browser_plugin_guest.cc | 87 VLOG(0) << "Guest crashed status: " << status; 106 // Check if we already observed a guest crash, return immediately if so.
|
/external/chromium_org/third_party/mesa/src/docs/ |
contents.html | 67 <li><a href="vmware-guest.html" target="MainFrame">VMware SVGA3D guest driver</a>
|
/external/chromium_org/tools/telemetry/telemetry/core/ |
browser_finder.py | 57 options.browser_type != 'cros-chrome-guest' and 60 '--remote requires --browser=cros-chrome or cros-chrome-guest.')
|
/external/qemu/android/camera/ |
camera-capture.h | 102 * Apparently, camera framework in the guest will only accept the the YV12 104 * pixel formats, supported by the camera device back to the guest. We can simpy
|
/external/qemu/ |
vnc.h | 119 struct VncSurface guest; /* guest visible surface (aka ds->surface) */ member in struct:VncState
|
/external/valgrind/main/coregrind/ |
pub_core_dispatch_asm.h | 34 /* Magic values that the guest state might be set to when returning to the 36 start of the thread's VEX guest state. These also are return values from
|