From: Stefan Hajnoczi <stefanha@gmail.com>
To: David Marchand <david.marchand@6wind.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
kvm@vger.kernel.org, claudio.fontana@huawei.com,
qemu-devel@nongnu.org, armbru@redhat.com,
arei.gonglei@huawei.com, mkletzan@redhat.com,
pbonzini@redhat.com, jani.kokkonen@huawei.com,
cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v5 1/3] contrib: add ivshmem client and server
Date: Fri, 5 Sep 2014 11:40:34 +0100 [thread overview]
Message-ID: <20140905104034.GC27649@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1409835061-19989-2-git-send-email-david.marchand@6wind.com>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
On Thu, Sep 04, 2014 at 02:50:59PM +0200, David Marchand wrote:
> When using ivshmem devices, notifications between guests can be sent as
> interrupts using a ivshmem-server (typical use described in documentation).
> The client is provided as a debug tool.
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> Signed-off-by: David Marchand <david.marchand@6wind.com>
> ---
> Makefile | 8 +
> configure | 3 +
> contrib/ivshmem-client/ivshmem-client.c | 405 +++++++++++++++++++++++++++++++
> contrib/ivshmem-client/ivshmem-client.h | 239 ++++++++++++++++++
> contrib/ivshmem-client/main.c | 237 ++++++++++++++++++
> contrib/ivshmem-server/ivshmem-server.c | 395 ++++++++++++++++++++++++++++++
> contrib/ivshmem-server/ivshmem-server.h | 186 ++++++++++++++
> contrib/ivshmem-server/main.c | 244 +++++++++++++++++++
> qemu-doc.texi | 10 +-
> 9 files changed, 1724 insertions(+), 3 deletions(-)
> create mode 100644 contrib/ivshmem-client/ivshmem-client.c
> create mode 100644 contrib/ivshmem-client/ivshmem-client.h
> create mode 100644 contrib/ivshmem-client/main.c
> create mode 100644 contrib/ivshmem-server/ivshmem-server.c
> create mode 100644 contrib/ivshmem-server/ivshmem-server.h
> create mode 100644 contrib/ivshmem-server/main.c
Modulo Michael's comments:
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-09-05 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 12:50 [Qemu-devel] [PATCH v5 0/3] ivshmem: update documentation, add client/server tools David Marchand
2014-09-04 12:50 ` [Qemu-devel] [PATCH v5 1/3] contrib: add ivshmem client and server David Marchand
2014-09-04 15:56 ` Michael S. Tsirkin
2014-09-05 8:52 ` Claudio Fontana
2014-09-05 12:07 ` David Marchand
2014-09-07 5:58 ` Michael S. Tsirkin
2014-09-04 15:58 ` Michael S. Tsirkin
2014-09-05 10:40 ` Stefan Hajnoczi [this message]
2014-09-04 12:51 ` [Qemu-devel] [PATCH v5 2/3] docs: update ivshmem device spec David Marchand
2014-09-05 10:30 ` Stefan Hajnoczi
2014-09-04 12:51 ` [Qemu-devel] [PATCH v5 3/3] ivshmem: add check on protocol version in QEMU David Marchand
2014-09-05 10:29 ` Stefan Hajnoczi
2014-09-05 12:25 ` David Marchand
2014-09-08 8:30 ` Stefan Hajnoczi
2014-09-04 15:40 ` [Qemu-devel] [PATCH v5 0/3] ivshmem: update documentation, add client/server tools Michael S. Tsirkin
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=20140905104034.GC27649@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=arei.gonglei@huawei.com \
--cc=armbru@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=claudio.fontana@huawei.com \
--cc=david.marchand@6wind.com \
--cc=jani.kokkonen@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=mkletzan@redhat.com \
--cc=olivier.matz@6wind.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).