From: Christian Pinto <c.pinto@virtualopensystems.com>
To: virtio-dev@lists.oasis-open.org
Cc: Baptiste Reynal <b.reynal@virtualopensystems.com>,
Jani Kokkonen <Jani.Kokkonen@huawei.com>,
Claudio Fontana <Claudio.Fontana@huawei.com>,
VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [virtio-dev] New virtio device specification
Date: Fri, 10 Jun 2016 10:01:05 +0200 [thread overview]
Message-ID: <CAFZJSOeGm6H=-i6ya+U0OFZ57cWtshCmHNhjMr8L74x5PL_itg@mail.gmail.com> (raw)
Hi all,
we are working on a new virtio device, 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.
For more details you can have a look at the following link:
https://lists.gnu.org/archive/html/qemu-devel/2016-03/msg04492.html
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/tree/sdm_test_virtio_mod_v1/
I am writing to understand how to start the procedure to include this
device in
the virtio specification and get a virtio device ID assigned.
Thanks in advance for your feedback.
Best regards,
Christian
next reply other threads:[~2016-06-10 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 8:01 Christian Pinto [this message]
2016-06-10 8:15 ` [Qemu-devel] [virtio-dev] New virtio device specification Cornelia Huck
2016-06-10 8:52 ` 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='CAFZJSOeGm6H=-i6ya+U0OFZ57cWtshCmHNhjMr8L74x5PL_itg@mail.gmail.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).