From: Andrew James <andrew.james@hpe.com>
To: "Marc-André Lureau" <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>
Subject: Re: [Qemu-devel] ivshmem property size should be a size, not a string
Date: Mon, 23 Nov 2015 16:29:30 -0700 [thread overview]
Message-ID: <5653A15A.1010703@hpe.com> (raw)
In-Reply-To: <243512039.12566588.1448050691647.JavaMail.zimbra@redhat.com>
On 11/20/2015 01:18 PM, Marc-André Lureau wrote:
> Hi
>
> ----- Original Message -----
>>>> Hash ivshmem been used in anger? If yes, how?
>>
>> Still the question to answer.
>
> I don't expect users to read this ML everyday (anybody actually). Personally, 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-case.
>> Why is this a single device model?
>
> 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,
--
Andrew James
next prev parent reply other threads:[~2015-11-23 23:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 16:07 [Qemu-devel] ivshmem property size should be a size, not a string Markus Armbruster
2015-11-20 16:23 ` Marc-André Lureau
2015-11-20 16:46 ` Eric Blake
2015-11-20 18:06 ` Markus Armbruster
2015-11-20 18:20 ` Marc-André Lureau
2015-11-20 19:39 ` Markus Armbruster
2015-11-20 20:18 ` Marc-André Lureau
2015-11-23 10:19 ` Markus Armbruster
2015-11-23 12:15 ` Marc-André Lureau
2015-11-23 13:25 ` Markus Armbruster
2015-11-23 13:48 ` Marc-André Lureau
2015-11-23 14:08 ` Markus Armbruster
2015-11-23 14:16 ` Marc-André Lureau
2015-11-23 14:46 ` Markus Armbruster
2015-11-23 14:53 ` Marc-André Lureau
2015-11-23 15:17 ` Markus Armbruster
2015-11-23 19:52 ` Eric Blake
2015-11-23 20:19 ` Marc-André Lureau
2015-11-24 9:56 ` Markus Armbruster
2015-11-24 12:23 ` Marc-André Lureau
2015-11-24 13:50 ` Markus Armbruster
2015-11-24 14:23 ` Marc-André Lureau
2015-11-24 15:12 ` Markus Armbruster
2015-11-23 18:22 ` Markus Armbruster
2015-11-23 23:29 ` Andrew James [this message]
2015-11-24 9:52 ` Markus Armbruster
2015-11-23 20:57 ` Bruce Rogers
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=5653A15A.1010703@hpe.com \
--to=andrew.james@hpe.com \
--cc=armbru@redhat.com \
--cc=claudio.fontana@huawei.com \
--cc=lcapitulino@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mlureau@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.