Lines Matching refs:its

18 infrastructure, a guest that compromised its hypervisor could
28 it needs to perform its job.
45 it needs to provide its service, e.g., a disk service could be given
80 code to emulate a device named "foo" is always present in QEMU, but its
84 The object model is hierarchical, so device emulation code names its
194 QEMU one. This could be useful for disk device emulation, since its
218 processes will provide are specified on its command line, as they would
227 *file0* as its backend.
294 channel during its initialization.
338 perform tasks related to being a proxy, such are registering its own
358 device emulator would perform in its initialization code, but with its
367 emulation object, but by its PCI parent object. Much of this space is
386 incoming interrupt indication would then be sent up to its bus parent to
448 *vmstate*. When the proxy is resumed on its new host, this *vmstate*
636 MMIO type (e.g., load or store), and its length and data. It also
704 executes certain ``ioctl()`` operations on its KVM file descriptor. They
710 ``ioctl()`` on its per-VM file descriptor. It will allocate and
751 The slave descriptor will have its own file operations vector, which
849 device has not de-asserted its interrupt.
868 descriptor from its route, then assigning it the new route. (see