From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Ilya Maximets" <i.maximets@samsung.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] memfd fixes.
Date: Mon, 11 Mar 2019 14:14:37 +0000 [thread overview]
Message-ID: <20190311141437.GA12393@redhat.com> (raw)
In-Reply-To: <20190311141229.GK8899@habkost.net>
On Mon, Mar 11, 2019 at 11:12:29AM -0300, Eduardo Habkost wrote:
> On Mon, Mar 11, 2019 at 12:56:14PM +0000, Daniel P. Berrangé wrote:
> > On Mon, Mar 11, 2019 at 01:50:37PM +0100, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Mon, Mar 11, 2019 at 1:35 PM Ilya Maximets <i.maximets@samsung.com> wrote:
> > > >
> > > > Hi.
> > > >
> > > > I'm trying to figure out the state of this patch set.
> > > > Is there any chance for it to be accepted?
> > > >
> > > > The first patch needs minor rebase. I could send a new version.
> > >
> > > Please do,
> > >
> > > I prefer the solution proposed in v2: do not register hostmem-memfd if
> > > sealing isn't supported (keep sealing=true the default - it's one of
> > > the main purpose of memfd imho).
> > >
> > > Daniel, Eduardo: are you ok with this series for 4.0?
> >
> > I prefer the more flexible approach, but I won't object to tieing memfd
> > to sealing support.
>
> Daniel, Marc-André: do you know if the libvirt QEMU capability
> cache is invalidated when the host kernel version changes?
Yes kernl version is one of the many invalidation criteria:
https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/qemu/qemu_capabilities.c;h=c9700193fd0c404c16dd6f334b80255a4d1ba605;hb=HEAD#l4072
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2019-03-11 14:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181127135037eucas1p18867a9ae8b1f2731ad4ce8d79fddae33@eucas1p1.samsung.com>
2018-11-27 13:50 ` [Qemu-devel] [PATCH v2 0/4] memfd fixes Ilya Maximets
[not found] ` <CGME20181127135045eucas1p1e259cacbab5e715f7845b9beee22f882@eucas1p1.samsung.com>
2018-11-27 13:50 ` [Qemu-devel] [PATCH v2 1/4] hostmem-memfd: disable for systems wihtout sealing support Ilya Maximets
2018-11-27 13:56 ` Marc-André Lureau
2018-12-10 16:18 ` Igor Mammedov
2018-12-11 10:29 ` Ilya Maximets
2018-12-11 15:48 ` Igor Mammedov
2019-01-05 2:43 ` Eduardo Habkost
2019-01-16 10:57 ` Ilya Maximets
2018-12-11 10:53 ` Daniel P. Berrangé
2018-12-11 11:09 ` Ilya Maximets
2018-12-12 6:49 ` Gerd Hoffmann
2019-01-16 15:30 ` Eduardo Habkost
2019-01-16 15:46 ` Ilya Maximets
2019-01-16 15:48 ` Daniel P. Berrangé
2019-01-16 15:54 ` Ilya Maximets
2019-01-16 15:56 ` Daniel P. Berrangé
2019-01-16 16:10 ` Eduardo Habkost
[not found] ` <CGME20181127135052eucas1p2cec316cce9b9218e4ab476315fd4596b@eucas1p2.samsung.com>
2018-11-27 13:50 ` [Qemu-devel] [PATCH v2 2/4] memfd: always check for MFD_CLOEXEC Ilya Maximets
[not found] ` <CGME20181127135059eucas1p2371079ab1d368d8d444d6a183719cfc7@eucas1p2.samsung.com>
2018-11-27 13:50 ` [Qemu-devel] [PATCH v2 3/4] memfd: set up correct errno if not supported Ilya Maximets
[not found] ` <CGME20181127135106eucas1p119ab7de9758f13ea52adc0f4829ab9cb@eucas1p1.samsung.com>
2018-11-27 13:50 ` [Qemu-devel] [PATCH v2 4/4] memfd: improve error messages Ilya Maximets
2019-03-11 12:34 ` [Qemu-devel] [PATCH v2 0/4] memfd fixes Ilya Maximets
2019-03-11 12:50 ` Marc-André Lureau
2019-03-11 12:56 ` Daniel P. Berrangé
2019-03-11 14:12 ` Eduardo Habkost
2019-03-11 14:14 ` Daniel P. Berrangé [this message]
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=20190311141437.GA12393@redhat.com \
--to=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=i.maximets@samsung.com \
--cc=imammedo@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@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 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).