From: Eduardo Habkost <ehabkost@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: imammedo@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 2/3] Add memfd based hostmem
Date: Mon, 3 Jul 2017 11:34:34 -0300 [thread overview]
Message-ID: <20170703143434.GH12152@localhost.localdomain> (raw)
In-Reply-To: <CAJ+F1C+79Hfd+7J2nS7=+4awjW6nqGSaVrWDx9P8O-8FCuBsdQ@mail.gmail.com>
On Thu, Jun 29, 2017 at 01:34:22PM +0000, Marc-André Lureau wrote:
> Hi
>
> On Wed, Jun 28, 2017 at 8:29 PM Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> > On Tue, Jun 27, 2017 at 08:23:03AM +0000, Marc-André Lureau wrote:
> > > Hi Eduardo
> > >
> > > On Fri, Jun 23, 2017 at 11:09 PM Eduardo Habkost <ehabkost@redhat.com>
> > > wrote:
> > >
> > > > On Wed, Jun 21, 2017 at 04:02:18PM +0200, Marc-André Lureau wrote:
> > > > > Add a new memory backend, similar to hostmem-file, except that it
> > > > > doesn't need to create files. It also enforces memory sealing.
> > > > >
> > > > > This backend is mainly useful for sharing the memory with other
> > > > > processes.
> > > >
> > > > How exactly can the memfd be used to share memory? Is there an
> > existing
> > > > mechanism for sharing the memfd file descriptor with another process
> > >
> > >
> > >
> > > Since there is no backing file, the traditional mechanism is by passing
> > fd,
> > > via socket ancillary data or forking etc.. Both ivshmem and vhost-user
> > have
> > > such messages, with eventually details for the memory map usage.
> >
> > The documentation is very similar to memory-backend-file, so it sounded
> > like there was a generic mechanism to ask QEMU to share the backend FD.
> > Maybe it would be interesting to mention on which cases the FD can
> > actually be shared. Are ivshmem and vhost-user the only existing cases?
> >
> >
> Actually, vhost-user may be the only way today to get the fd outside of
> qemu process.
>
> (ivshmem needs the server to provide the fd)
>
> We could quite easily add or extend QMP messages for that in the future.
>
> Do you want this detail to be written in the commit message or elsewhere?
(Sorry for taking so long to reply.)
I think this should be in the documentation of the new option (in
qemu-options.hx).
I don't think it needs lots of extra detail, maybe just change "which
can be used to share the memory with a co-operating external process" to
"which allows QEMU to share the memory with an external process in some
cases (e.g. when using vhost-user)".
--
Eduardo
next prev parent reply other threads:[~2017-07-03 14:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 14:02 [Qemu-devel] [PATCH v4 0/3] Add memfd memory backend Marc-André Lureau
2017-06-21 14:02 ` [Qemu-devel] [PATCH v4 1/3] memfd: split qemu_memfd_alloc() Marc-André Lureau
2017-06-21 14:02 ` [Qemu-devel] [PATCH v4 2/3] Add memfd based hostmem Marc-André Lureau
2017-06-23 21:08 ` Eduardo Habkost
2017-06-27 8:23 ` Marc-André Lureau
2017-06-28 18:29 ` Eduardo Habkost
2017-06-29 13:34 ` Marc-André Lureau
2017-07-03 14:34 ` Eduardo Habkost [this message]
2017-06-21 14:02 ` [Qemu-devel] [PATCH v4 3/3] tests: use memfd in vhost-user-test Marc-André Lureau
2017-06-22 9:58 ` [Qemu-devel] [PATCH v4 0/3] Add memfd memory backend David Hildenbrand
2017-06-23 11:29 ` Eduardo Habkost
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=20170703143434.GH12152@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcandre.lureau@gmail.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 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).