From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0vkc-0007Tx-RL for qemu-devel@nongnu.org; Mon, 23 Nov 2015 13:22:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a0vkZ-00031H-Oe for qemu-devel@nongnu.org; Mon, 23 Nov 2015 13:22:06 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60146) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0vkZ-00031D-Jb for qemu-devel@nongnu.org; Mon, 23 Nov 2015 13:22:03 -0500 From: Markus Armbruster References: <87si401wpf.fsf@blackfin.pond.sub.org> <2083526024.12459505.1448036588653.JavaMail.zimbra@redhat.com> <564F4E68.8090903@redhat.com> <87si40sfzh.fsf@blackfin.pond.sub.org> <430569618.12530858.1448043657890.JavaMail.zimbra@redhat.com> <874mggo3yc.fsf@blackfin.pond.sub.org> <243512039.12566588.1448050691647.JavaMail.zimbra@redhat.com> <87oael587p.fsf@blackfin.pond.sub.org> Date: Mon, 23 Nov 2015 19:22:00 +0100 In-Reply-To: <87oael587p.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Mon, 23 Nov 2015 11:19:22 +0100") Message-ID: <87io4sinjr.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] ivshmem property size should be a size, not a string List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?utf-8?Q?Marc-Andr=C3=A9?= Lureau Cc: marcandre lureau , Claudio Fontana , qemu-devel@nongnu.org, Luiz Capitulino Markus Armbruster writes: > Marc-Andr=C3=A9 Lureau writes: [...] >>> * shm appears to be the same as memdev, just less flexible. Why does it >>> exist? >> >> It was there before. > > Not only is memdev more flexible, it also provides the clean split > between frontend and backend we generally want. In my tests, shm=3Dfoo can indeed be replaced by -object memory-backend=3Dfile,mem-path=3D/dev/shm/foo. However, /dev/shm is Linux-specific. For portability, we might need a memory-backend-shm. [...]