Lines Matching full:qemu
37 through a high-speed communication channel called a "QEMU Pipe".
55 | QEMU PIPE |
121 | QEMU PIPE |
172 For various practical reasons, we plan to completely separate the core QEMU
175 need to receive protocol bytes from the QEMU process.
185 code inside the QEMU code base which is terribly complex.
210 - The emulator sources are under $ANDROID/external/qemu, which we'll
211 call $QEMU in the rest of this document.
219 - The QEMU Pipe kernel driver is under $KERNEL/drivers/misc/qemupipe
222 $KERNEL is the top of the qemu-specific kernel source tree (using one
227 $QEMU/hw/goldfish_pipe.c -> implement QEMU pipe virtual hardware
228 $QEMU/hw/opengles.c -> implement GLES initialization
229 $QEMU/hw/hw-pipe-net.c -> implements the communication channel
230 between the QEMU Pipe and the renderer library
343 an alternative QEMU-specific source:
346 -> uses QEMU pipe from the guest
348 The QEMU Pipe implementation is _significantly_ faster (about 20x) due to
539 to the renderer through the QEMU Pipe instead.
542 because memory copies inside the guest are slow, while QEMU pipe transfers
593 The code under $QEMU/android/opengles.c is in charge of dynamically loading
596 QEMU pipe connections to the 'opengles' service are piped through the code
597 in $QEMU/android/hw-pipe-net.c. Look for the openglesPipe_init() function,
604 (through the renderer library's subwindow) under $QEMU/skin/window.
