Lines Matching full:pipe
37 through a high-speed communication channel called a "QEMU Pipe".
39 For now, all you need to know is that the pipe is implemented with a
55 | QEMU PIPE |
121 | QEMU PIPE |
178 named pipe between these two. A shared memory segment with appropriate
216 - The QEMU Pipe kernel driver is under $KERNEL/drivers/misc/qemupipe
224 $QEMU/hw/goldfish_pipe.c -> implement QEMU pipe virtual hardware
226 $QEMU/hw/hw-pipe-net.c -> implements the communication channel
227 between the QEMU Pipe and the renderer library
331 $EMUGL/system/OpenglSystemCommon/QemuPipeStream.cpp -> uses QEMU pipe from the guest
333 The QEMU Pipe implementation is _significantly_ faster (about 20x) due to
519 to the renderer through the QEMU Pipe instead.
522 because memory copies inside the guest are slow, while QEMU pipe transfers
555 (on Linux and OS X), or to a Win32 named pipe (on Windows). To do so, one
575 QEMU pipe connections to the 'opengles' service are piped through the code
576 in $QEMU/android/hw-pipe-net.c. Look for the openglesPipe_init() function,
578 (either through a TCP socket, or a Unix pipe depending on configuration.
