From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:35858)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrew.james@hpe.com>) id 1a10YJ-0004QO-59
	for qemu-devel@nongnu.org; Mon, 23 Nov 2015 18:29:44 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andrew.james@hpe.com>) id 1a10YF-0005Ac-N2
	for qemu-devel@nongnu.org; Mon, 23 Nov 2015 18:29:43 -0500
Received: from g2t4622.austin.hp.com ([15.73.212.79]:47275)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andrew.james@hpe.com>) id 1a10YF-000581-GS
	for qemu-devel@nongnu.org; Mon, 23 Nov 2015 18:29:39 -0500
Message-ID: <5653A15A.1010703@hpe.com>
Date: Mon, 23 Nov 2015 16:29:30 -0700
From: Andrew James <andrew.james@hpe.com>
MIME-Version: 1.0
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>
In-Reply-To: <243512039.12566588.1448050691647.JavaMail.zimbra@redhat.com>
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: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= <mlureau@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: marcandre lureau <marcandre.lureau@redhat.com>, Claudio Fontana <claudio.fontana@huawei.com>, qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>

On 11/20/2015 01:18 PM, Marc-Andr=C3=A9 Lureau wrote:
> Hi
>=20
> ----- Original Message -----
>>>> Hash ivshmem been used in anger?  If yes, how?
>>
>> Still the question to answer.
>=20
> I don't expect users to read this ML everyday (anybody actually). Perso=
nally, I have no clue how widespread ivshmem usage is.

We (Hewlett Packard Enterprise) are using ivshmem as a part of a project
that is set to go public in the next few days:

https://github.com/FabricAttachedMemory

Sorry for the premature announcement; I wanted to declare our interest
in ivshmem itself. QEMU 2.1 through 2.4.1 have worked well for our use-ca=
se.

>>   Why is this a single device model?
>=20
> No idea, but I agree it would make sense to have two different devices.

FWIW, I support splitting the device into memdev and doorbell varieties
as long as a compatibility device is available too.


Thanks,
--=20
Andrew James