Hi, > +Current separation models > + > +In order to separate the device emulation code from the CPU emulation > +code, the device object code must run in a different process. There are > +a couple of existing QEMU features that can run emulation code > +separately from the main QEMU process. These are examined below.
There also is vfio+mdev. Right now a kernel interface, so (hardware-assisted) device emulation runs in the linux kernel. IIRC someone suggested to build a process->process interface based on the vfio api. What happened to that idea? > +If these devices are emulated by remote process “disk-proc,” as > +described in the previous section, the QEMU command line would be: > + > + -device lsi53c895a,id=scsi0,remote=disk-proc > + -device scsi-hd,drive=drive0,bus=scsi0.0,scsi-id=0,remote=disk-proc Does that work with the patch series? Why does qemu need to know about scsi-hd? cheers, Gerd
