Re: [PATCH RESEND v6 00/36] Initial support for multi-process qemu

[Jag Raman]

> On May 11, 2020, at 10:40 AM, Stefan Hajnoczi <address@hidden> wrote:
> 
> Hi,
> Have you decided whether to drop the remote device program in favor of
> using a softmmu make target?
> 
> Is there anything in this series you'd like me to review before you send
> the next revision?

Hi Stefan,

We are planning to drop the separate remote device program in the next
revision. We are planning to use QEMU’s existing event loop instead of
a separate event loop for the remote process, as well as the command
line invocation you suggested in your feedback.

We hope the following core patches look good to you, by and large:
[PATCH RESEND v6 01/36] memory: alloc RAM from file at offset
[PATCH RESEND v6 11/36] multi-process: define mpqemu-link object
[PATCH RESEND v6 12/36] multi-process: add functions to synchronize proxy and 
remote endpoints
[PATCH RESEND v6 13/36] multi-process: setup PCI host bridge for remote device
[PATCH RESEND v6 14/36] multi-process: setup a machine object for remote device 
process
[PATCH RESEND v6 15/36] multi-process: setup memory manager for remote device
[PATCH RESEND v6 17/36] multi-process: introduce proxy object
[PATCH RESEND v6 18/36] multi-process: Initialize Proxy Object's communication 
channel
[PATCH RESEND v6 19/36] multi-process: Connect Proxy Object with device in the 
remote process
[PATCH RESEND v6 20/36] multi-process: Forward PCI config space acceses to the 
remote process
[PATCH RESEND v6 21/36] multi-process: PCI BAR read/write handling for proxy & 
remote endpoints
[PATCH RESEND v6 22/36] multi-process: Synchronize remote memory
[PATCH RESEND v6 23/36] multi-process: create IOHUB object to handle irq
[PATCH RESEND v6 24/36] multi-process: Retrieve PCI info from remote process

Thank you very much!
—
Jag

> 
> Stefan