qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 0/4] memfd fixes.


From: Daniel P . Berrangé
Subject: Re: [Qemu-devel] [PATCH v2 0/4] memfd fixes.
Date: Mon, 11 Mar 2019 14:14:37 +0000
User-agent: Mutt/1.11.3 (2019-02-01)

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 <address@hidden> 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 :|



reply via email to

[Prev in Thread] Current Thread [Next in Thread]