From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47428) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alYgt-0006YD-S2 for qemu-devel@nongnu.org; Thu, 31 Mar 2016 05:15:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1alYgo-0002sU-Oc for qemu-devel@nongnu.org; Thu, 31 Mar 2016 05:14:59 -0400 Received: from mail-wm0-x22c.google.com ([2a00:1450:400c:c09::22c]:34754) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1alYgo-0002sI-Hl for qemu-devel@nongnu.org; Thu, 31 Mar 2016 05:14:54 -0400 Received: by mail-wm0-x22c.google.com with SMTP id p65so216016131wmp.1 for ; Thu, 31 Mar 2016 02:14:54 -0700 (PDT) Date: Thu, 31 Mar 2016 10:14:52 +0100 From: Stefan Hajnoczi Message-ID: <20160331091452.GF32185@stefanha-x1.localdomain> References: <1458292438-13909-1-git-send-email-b.reynal@virtualopensystems.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Y/WcH0a6A93yCHGr" Content-Disposition: inline In-Reply-To: <1458292438-13909-1-git-send-email-b.reynal@virtualopensystems.com> Subject: Re: [Qemu-devel] [RFC v2 0/6] QEMU shared-memory backend List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Baptiste Reynal Cc: Jani.Kokkonen@huawei.com, tech@virtualopensystems.com, Claudio.Fontana@huawei.com, qemu-devel@nongnu.org --Y/WcH0a6A93yCHGr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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. >=20 > 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. >=20 > 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? --Y/WcH0a6A93yCHGr Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJW/OqMAAoJEJykq7OBq3PII+oH/2PXaEOk+bn37qTzypdMOWJQ WG6Y+igEy8zEnM3c8a27+2nMgYXNe7epDRGEnByWfUaNgRvtk9+tBCizEJfHb6B4 UKhlUykF8TtULRMMuE9rehKPGUQCRekJIC23Cx+2tZkW756B23Z8ln5zpfV+L4I+ cS0olJ4e2Kojv6Pr8ppunGowVWJIx993yIpBV0NoBpWrmTMYRbqz+n3lYWDVnvEi TexFTNiWL8DC0uvELYJNAkq9igAOvp1pt8jisCdz9O7oE6mBhYGbByvNMiTB8a55 E/aR8x1ogZwVaKf/WcgZ1q2y+UiLbpu/piqJ1gqOJaXf0xqrMK8a0+/hc1zRH/k= =Cglh -----END PGP SIGNATURE----- --Y/WcH0a6A93yCHGr--