From: David Marchand <david.marchand@6wind.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, claudio.fontana@huawei.com,
pbonzini@redhat.com, jani.kokkonen@huawei.com,
cam@cs.ualberta.ca
Subject: [Qemu-devel] [PATCH v2 0/2] ivshmem: update documentation, add client/server tools
Date: Sun, 20 Jul 2014 11:38:37 +0200 [thread overview]
Message-ID: <1405849119-13569-1-git-send-email-david.marchand@6wind.com> (raw)
Here is a patchset containing an update on ivshmem specs documentation and
importing ivshmem server and client tools.
These tools have been written from scratch and are not related to what is
available in nahanni repository.
I put them in contrib/ directory as the qemu-doc.texi was already telling the
server was supposed to be there.
Changes since v1:
- moved client/server import patch before doc update,
- tried to re-organise the ivshmem_device_spec.txt file based on Claudio
comments (still not sure if the result is that great, comments welcome),
- incorporated comments from Claudio, Eric and Cam,
- added more details on the server <-> client messages exchange (but sorry, no
ASCII art here).
By the way, there are still some functionnalities that need description (use of
ioeventfd, the lack of irqfd support) and some parts of the ivshmem code clearly
need cleanup. I will try to address this in future patches when these first
patches are ok.
--
David Marchand
David Marchand (2):
contrib: add ivshmem client and server
docs: update ivshmem device spec
contrib/ivshmem-client/Makefile | 26 ++
contrib/ivshmem-client/ivshmem-client.c | 418 ++++++++++++++++++++++++++++++
contrib/ivshmem-client/ivshmem-client.h | 238 ++++++++++++++++++
contrib/ivshmem-client/main.c | 246 ++++++++++++++++++
contrib/ivshmem-server/Makefile | 26 ++
contrib/ivshmem-server/ivshmem-server.c | 420 +++++++++++++++++++++++++++++++
contrib/ivshmem-server/ivshmem-server.h | 185 ++++++++++++++
contrib/ivshmem-server/main.c | 296 ++++++++++++++++++++++
docs/specs/ivshmem_device_spec.txt | 124 ++++++---
qemu-doc.texi | 10 +-
10 files changed, 1955 insertions(+), 34 deletions(-)
create mode 100644 contrib/ivshmem-client/Makefile
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/Makefile
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
--
1.7.10.4
next reply other threads:[~2014-07-20 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 9:38 David Marchand [this message]
2014-07-20 9:38 ` [Qemu-devel] [PATCH v2 1/2] contrib: add ivshmem client and server David Marchand
2014-07-21 14:21 ` Eric Blake
2014-07-21 14:30 ` Daniel P. Berrange
2014-07-21 15:26 ` David Marchand
2014-07-21 17:35 ` Markus Armbruster
2014-08-08 8:49 ` David Marchand
2014-07-20 9:38 ` [Qemu-devel] [PATCH v2 2/2] docs: update ivshmem device spec David Marchand
2014-07-21 8:19 ` Claudio Fontana
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=1405849119-13569-1-git-send-email-david.marchand@6wind.com \
--to=david.marchand@6wind.com \
--cc=cam@cs.ualberta.ca \
--cc=claudio.fontana@huawei.com \
--cc=jani.kokkonen@huawei.com \
--cc=kvm@vger.kernel.org \
--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).