qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC v3 PATCH 00/45] Initial support of multi-process q


From: Jag Raman
Subject: Re: [Qemu-devel] [RFC v3 PATCH 00/45] Initial support of multi-process qemu
Date: Wed, 4 Sep 2019 12:29:57 -0400
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1



On 9/4/2019 5:18 AM, Daniel P. Berrangé wrote:
On Tue, Sep 03, 2019 at 04:37:26PM -0400, Jagannathan Raman wrote:
Started with the presentation in October 2017 made by Marc-Andre (Red Hat)
and Konrad Wilk (Oracle) [1], and continued by Jag's BoF at KVM Forum 2018,
the multi-process project is now a prototype and presented in this patchset.

This first series enables the emulation of lsi53c895a in a separate process.

We posted the Proof Of Concept patches [2] before the BoF session in 2018.
Subsequently, we posted RFC v1 [3] & RFC v2 [4] of this series.

Thanks to the v1 & v2 review, we were able to incorporate the feedback into
our goals.

In the summer of 2019, we participated in a conference with folks at RedHat,
who provided us with feedback to improve the design of this project.

We want to present version 3 of this series which incorporates the feedback
we received for v2 & the enhancements suggested in the conference. Following
are the improvements made in this series:

This patch series fails to apply to git master when I attempt and confirmed
by patchew's failed attempt too

   https://patchew.org/QEMU/address@hidden/

Can you do one of the following

  - Tell us what git hash it was based on instead of master

Hi Daniel,

These patches are based on the latest release, v4.1.0. They are on top
of the following git hash:
9e06029aea3 Update version for v4.1.0 release

or
  - provide a pointer to a publically accessible git repo with it applied

They are also publicly available from the following gitub repo.:
https://github.com/oracle/qemu.git  [branch multi-process-qemu-v0.3]

Thanks!
--
Jag

or
  - Repost with based on current git master

Regards,
Daniel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]