From: Christian Pinto <c.pinto@virtualopensystems.com>
To: virtio-dev@lists.oasis-open.org
Cc: qemu-devel@nongnu.org, b.reynal@virtualopensystems.com,
tech@virtualopensystems.com, Claudio.Fontana@huawei.com,
Jani.Kokkonen@huawei.com,
Christian Pinto <c.pinto@virtualopensystems.com>
Subject: [Qemu-devel] [virtio-dev][RFC 0/2] Signal Distribution Module virtio device specification
Date: Fri, 17 Jun 2016 18:03:12 +0200 [thread overview]
Message-ID: <1466179394-4744-1-git-send-email-c.pinto@virtualopensystems.com> (raw)
Hi all,
This patch series proposes the specification of a new virtio device on which we
are working on, namely the Signal Distribution Module (SDM).
The SDM routes inter-processor signals intra and inter QEMU
instances, using a user-defined communication channel. At the current state the
SDM provides a local channel, for intra-QEMU signals, and a channel based on
sockets (UNIX or TCP) to exchange signals between processors in different
instances of QEMU. Each communication channel exports a common interface for
the sake of ease of extension and integration of new channels.
In addition to the virtio version, a platform device version is available as
well to be used for cases where a processor is not running Linux but another
OS/firmware that does not support virtio.
This patch is related to :
[Qemu-devel][RFC v3 0/6] SDM Interface
where you can find the latest RFC patch set for the QEMU code of the virtio SDM
device.
Kernel code is publicly accessible from:
https://git.virtualopensystems.com/dev/qemu-het-tools
branch sdm_test_virtio_mod_v2.
QEMU code is accessible from:
https://git.virtualopensystems.com/dev/qemu-het-tools
branch sdm-dev-v3
Thanks,
Christian
Christian Pinto (2):
content: reserve virtio device ID
virtio-sdm: new device specification
content.tex | 4 ++
virtio-sdm.tex | 126 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 130 insertions(+)
create mode 100644 virtio-sdm.tex
--
1.9.1
next reply other threads:[~2016-06-17 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 16:03 Christian Pinto [this message]
2016-06-17 16:03 ` [Qemu-devel] [virtio-dev][RFC 1/2] content: reserve virtio device ID Christian Pinto
2016-06-23 18:57 ` Stefan Hajnoczi
2016-06-24 12:45 ` Christian Pinto
2016-06-24 13:04 ` Cornelia Huck
2016-06-24 14:08 ` Christian Pinto
2016-06-17 16:03 ` [Qemu-devel] [virtio-dev][RFC 2/2] virtio-sdm: new device specification Christian Pinto
2016-06-23 19:39 ` Stefan Hajnoczi
2016-06-24 12:39 ` Christian Pinto
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=1466179394-4744-1-git-send-email-c.pinto@virtualopensystems.com \
--to=c.pinto@virtualopensystems.com \
--cc=Claudio.Fontana@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=b.reynal@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.com \
--cc=virtio-dev@lists.oasis-open.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).