From: Stefan Hajnoczi <stefanha@gmail.com>
To: Baptiste Reynal <b.reynal@virtualopensystems.com>
Cc: Jani.Kokkonen@huawei.com, tech@virtualopensystems.com,
Claudio.Fontana@huawei.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC v2 0/6] QEMU shared-memory backend
Date: Thu, 31 Mar 2016 10:14:52 +0100 [thread overview]
Message-ID: <20160331091452.GF32185@stefanha-x1.localdomain> (raw)
In-Reply-To: <1458292438-13909-1-git-send-email-b.reynal@virtualopensystems.com>
[-- Attachment #1: Type: text/plain, Size: 589 bytes --]
On Fri, Mar 18, 2016 at 10:13:52AM +0100, Baptiste Reynal wrote:
> A new memory backend, the shared memory backend, based on
> the file memory backend.
>
> This new backend allows a master QEMU instance to share a part of
> his main memory whith a slave QEMU instance. It is then possible to load
> a firmware on this memory and trigger the slave boot using a SDM
> signal.
>
> Such new backend enables, on a master side, to allocate the whole
> memory as shareable (e.g. /dev/shm, or hugetlbfs).
How is this different from qemu -mem-path which can be used for
hugetlbfs?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-31 9:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 9:13 [Qemu-devel] [RFC v2 0/6] QEMU shared-memory backend Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 1/6] backend: shared memory backend Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 2/6] migration: add shared migration type Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 3/6] hw/misc: sdm signal shboot Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 4/6] qemu: slave machine flag Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 5/6] hw/arm: boot Baptiste Reynal
2016-03-18 9:13 ` [Qemu-devel] [RFC v2 6/6] qemu: numa Baptiste Reynal
2016-03-22 14:14 ` [Qemu-devel] [RFC v2 0/6] QEMU shared-memory backend Markus Armbruster
2016-03-22 14:54 ` Baptiste Reynal
2016-04-07 16:27 ` Markus Armbruster
2016-04-08 12:52 ` Baptiste Reynal
2016-04-08 13:59 ` Markus Armbruster
2016-03-31 9:14 ` Stefan Hajnoczi [this message]
2016-04-05 12:00 ` Baptiste Reynal
2016-04-06 8:57 ` Stefan Hajnoczi
2016-04-06 13:47 ` Igor Mammedov
2016-04-08 12:46 ` Baptiste Reynal
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=20160331091452.GF32185@stefanha-x1.localdomain \
--to=stefanha@gmail.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 \
/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).