[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170414094740.GN784@bombadil.infradead.org>
Date: Fri, 14 Apr 2017 02:47:40 -0700
From: Matthew Wilcox <willy@...radead.org>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: Wei Wang <wei.w.wang@...el.com>, virtio-dev@...ts.oasis-open.org,
linux-kernel@...r.kernel.org, qemu-devel@...gnu.org,
virtualization@...ts.linux-foundation.org, kvm@...r.kernel.org,
linux-mm@...ck.org, david@...hat.com, dave.hansen@...el.com,
cornelia.huck@...ibm.com, akpm@...ux-foundation.org,
mgorman@...hsingularity.net, aarcange@...hat.com,
amit.shah@...hat.com, pbonzini@...hat.com,
liliang.opensource@...il.com
Subject: Re: [PATCH v9 0/5] Extend virtio-balloon for fast (de)inflating &
fast live migration
On Fri, Apr 14, 2017 at 04:50:48AM +0300, Michael S. Tsirkin wrote:
> On Thu, Apr 13, 2017 at 01:44:11PM -0700, Matthew Wilcox wrote:
> > On Thu, Apr 13, 2017 at 05:35:03PM +0800, Wei Wang wrote:
> > > 2) transfer the guest unused pages to the host so that they
> > > can be skipped to migrate in live migration.
> >
> > I don't understand this second bit. You leave the pages on the free list,
> > and tell the host they're free. What's preventing somebody else from
> > allocating them and using them for something? Is the guest semi-frozen
> > at this point with just enough of it running to ask the balloon driver
> > to do things?
>
> There's missing documentation here.
>
> The way things actually work is host sends to guest
> a request for unused pages and then write-protects all memory.
... hopefully you mean "write protects all memory, then sends a request
for unused pages", otherwise there's a race condition.
And I see the utility of this, but does this functionality belong in
the balloon driver? It seems like it's something you might want even
if you don't have the balloon driver loaded. Or something you might
not want if you do have the balloon driver loaded.
Powered by blists - more mailing lists