docs/devel/multi-process.rst

48 this service would not be able to use this exploit to access files or
51 A QEMU control process would remain, but in multi-process mode, will
52 have no direct interfaces to the VM. During VM execution, it would still
56 from the main QEMU program, which would continue to provide CPU
57 emulation. i.e., the control process would also be the CPU emulation
131 vhost user device, the memory operation would need to be sent over a
203 rest of this section is a discussion of how a proxy object model would
211 QEMU code, because for anything but the simplest device, it would not be
218 processes will provide are specified on its command line, as they would
226 would indicate process *disk-proc* uses a qcow2 emulated disk named
319 which any other QEMU device would be initialized.
337 The ``instance_init()`` and ``realize()`` functions would only need to
357 A proxy object would need to mirror the memory region calls the actual
358 device emulator would perform in its initialization code, but with its
376 proxy object. This class's parent would be "pci-device" and it would
386 incoming interrupt indication would then be sent up to its bus parent to
407 DMA operations would be handled much like vhost applications do. One of
484 would then be added to the *system\_memory* memory region with
523 an emulation process would be to setup the root PCI bus driver (via
533 into the VM. A simple emulation process implementation would be to send
588 The KVM file descriptors created would be passed to the emulation process
598 The expanded idea would require a new type of KVM device:
602 would create both descriptors using the KVM driver, and pass the slave
668 threads may be waiting for MMIO replies. The scoreboard would contain a
695 The descriptor would be returned by the KVM driver when QEMU issues a
834 This performance optimization would work much like a vhost user
902 After IO services have been disaggregated, a second phase would be to
905 code, so the first task would be to create one.
922 ID, and the third for all other user IDs. Each device instance would
963 category. The different device emulation processes would not be able to
967 scheme described above. In this scenario, different categories would be