qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Baptiste Reynal <b.reynal@virtualopensystems.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu list <qemu-devel@nongnu.org>,
	Jani.Kokkonen@huawei.com,
	VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
	Claudio.Fontana@huawei.com, Daniel Berrange <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] backend: multi-client-socket
Date: Fri, 8 Apr 2016 15:18:44 +0200	[thread overview]
Message-ID: <CAN9JPjHBYFPPNTXE5wZKNOE5=jkTDoRuupHWpwngbhu-Zndw1w@mail.gmail.com> (raw)
In-Reply-To: <20160331090808.GD32185@stefanha-x1.localdomain>

I wasn't aware of this new framework when I started the development of
this socket. For sure I'll have a deeper look and see what can be
shared for the next version.

On Thu, Mar 31, 2016 at 11:08 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Fri, Mar 18, 2016 at 10:12:46AM +0100, Baptiste Reynal wrote:
>> This patch introduces a new socket for QEMU, called multi-client-socket. This
>> socket allows multiple QEMU instances to communicate by sharing messages
>> and file descriptors.
>>
>> A socket can be instantiated with the following parameters:
>> -object multi-socket-backend,id=<id>,path=<socket_path>,listen=<on/off>
>>
>> If listen is set, the socket will act as a listener and register new
>> clients.
>>
>> This patch is a follow-up to "[RFC PATCH 0/8] Towards an Heterogeneous QEMU":
>> https://lists.gnu.org/archive/html/qemu-devel/2015-10/msg00171.html
>>
>> This work has been sponsored by Huawei Technologies Duesseldorf GmbH.
>>
>> Signed-off-by: Baptiste Reynal <b.reynal@virtualopensystems.com>
>> ---
>>  backends/Makefile.objs      |   2 +
>>  backends/multi-socket.c     | 355 ++++++++++++++++++++++++++++++++++++++++++++
>>  include/qemu/multi-socket.h | 124 ++++++++++++++++
>>  3 files changed, 481 insertions(+)
>>  create mode 100644 backends/multi-socket.c
>>  create mode 100644 include/qemu/multi-socket.h
>
> Is it possible to reuse QEMU's UNIX domain socket and fd passing code?
> For example, take a look at io/channel-socket.c.

      reply	other threads:[~2016-04-08 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18  9:12 [Qemu-devel] [PATCH 1/1] backend: multi-client-socket Baptiste Reynal
2016-03-31  9:08 ` Stefan Hajnoczi
2016-04-08 13:18   ` Baptiste Reynal [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN9JPjHBYFPPNTXE5wZKNOE5=jkTDoRuupHWpwngbhu-Zndw1w@mail.gmail.com' \
    --to=b.reynal@virtualopensystems.com \
    --cc=Claudio.Fontana@huawei.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=tech@virtualopensystems.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).