From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Jailhouse <jailhouse-dev@googlegroups.com>
Subject: Re: [Qemu-devel] Towards an ivshmem 2.0?
Date: Mon, 16 Jan 2017 14:18:55 +0000 [thread overview]
Message-ID: <20170116141855.GH14681@stefanha-x1.localdomain> (raw)
In-Reply-To: <8a51513f-59d7-a361-a4ef-99679aa460fb@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Mon, Jan 16, 2017 at 09:36:51AM +0100, Jan Kiszka wrote:
> some of you may know that we are using a shared memory device similar to
> ivshmem in the partitioning hypervisor Jailhouse [1].
>
> We started as being compatible to the original ivshmem that QEMU
> implements, but we quickly deviated in some details, and in the recent
> months even more. Some of the deviations are related to making the
> implementation simpler. The new ivshmem takes <500 LoC - Jailhouse is
> aiming at safety critical systems and, therefore, a small code base.
> Other changes address deficits in the original design, like missing
> life-cycle management.
My first thought is "what about virtio?". Can you share some background
on why ivshmem fits the use case better than virtio?
The reason I ask is because the ivshmem devices you define would have
parallels to existing virtio devices and this could lead to duplication.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2017-01-16 14:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 8:36 [Qemu-devel] Towards an ivshmem 2.0? Jan Kiszka
2017-01-16 12:41 ` Marc-André Lureau
2017-01-16 13:10 ` Jan Kiszka
2017-01-17 9:13 ` Wang, Wei W
2017-01-17 9:46 ` Jan Kiszka
2017-01-20 11:54 ` Wang, Wei W
2017-01-20 16:37 ` Jan Kiszka
2017-01-23 3:49 ` Wang, Wei W
2017-01-23 10:14 ` Måns Rullgård
2017-01-17 9:59 ` Stefan Hajnoczi
2017-01-17 10:32 ` Jan Kiszka
2017-01-29 11:56 ` msuchanek
2017-01-30 11:25 ` Stefan Hajnoczi
2017-01-16 14:18 ` Stefan Hajnoczi [this message]
2017-01-16 14:34 ` Jan Kiszka
2017-01-17 10:00 ` Stefan Hajnoczi
2017-01-23 14:19 ` Markus Armbruster
2017-01-25 9:18 ` Jan Kiszka
2017-01-27 19:36 ` Markus Armbruster
2017-01-29 8:43 ` Jan Kiszka
2017-01-29 14:00 ` Marc-André Lureau
2017-01-29 14:14 ` Jan Kiszka
2017-01-30 8:02 ` Markus Armbruster
2017-01-30 8:05 ` Jan Kiszka
2017-01-31 2:51 ` Wang, Wei W
2017-01-30 8:00 ` Markus Armbruster
2017-01-30 8:14 ` Jan Kiszka
2017-01-30 12:19 ` Markus Armbruster
2017-01-30 15:57 ` Jan Kiszka
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=20170116141855.GH14681@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.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).