qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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, cornelia.huck@de.ibm.com,
	stefanha@redhat.com,
	Christian Pinto <c.pinto@virtualopensystems.com>
Subject: [Qemu-devel] [virtio-dev][RFC v2 0/2] Signal Distribution Module virtio device specification
Date: Tue, 28 Jun 2016 13:03:42 +0200	[thread overview]
Message-ID: <1467111824-11548-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 using a user-defined communication 
channel. A possible use-case of the SDM is an AMP system where the vairous processors
need to exhange signals (e.g., interrupts) to implement inter-processor
communication patterns. An example are RPMSG and remoteproc, both using
interrupts to kick the virtio queues used for communication (RPMSG), and a boot
signal to start the execution of a slave processor (remoteproc).

However the SDM is not limited to those use-cases and can be easily extended to
support user-defined signals and communication 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 series is related to :

[Qemu-devel][RFC v3 0/6] SDM Interface
https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg05121.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

branch sdm_test_virtio_mod_v2.

QEMU code is accessible from:

https://git.virtualopensystems.com/dev/qemu-het-tools

branch sdm-dev-v3

At the current state the SDM is implemented as a QEMU device and 
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.


Thanks,

Christian

---
Changes since v1:
- Fixed some typos
- Removed dependencies from QEMU
- Added explanation on how SDM can be used in AMP systems
- Explained semantics of payload field in SDMSignalData struct
---

Christian Pinto (2):
  content: reserve virtio device ID
  virtio-sdm: new device specification

 content.tex    |   4 ++
 virtio-sdm.tex | 128 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 132 insertions(+)
 create mode 100644 virtio-sdm.tex

-- 
1.9.1

             reply	other threads:[~2016-06-28 11:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-28 11:03 Christian Pinto [this message]
2016-06-28 11:03 ` [Qemu-devel] [virtio-dev][RFC v2 1/2] content: reserve virtio device ID Christian Pinto
2016-07-14 12:16   ` Stefan Hajnoczi
2016-07-14 12:22   ` Stefan Hajnoczi
2016-06-28 11:03 ` [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification Christian Pinto
2016-07-14 12:17   ` Stefan Hajnoczi
2016-07-19  7:47     ` Christian Pinto
2016-07-19  8:40       ` Stefan Hajnoczi
2016-07-22 16:18         ` Christian Pinto
2016-08-04  8:46           ` Stefan Hajnoczi
2016-08-08  8:00             ` Christian Pinto
2016-07-14 12:24   ` Stefan Hajnoczi

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=1467111824-11548-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=cornelia.huck@de.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).