[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161021224428-mutt-send-email-mst@kernel.org>
Date: Fri, 21 Oct 2016 22:44:37 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Liang Li <liang.z.li@...el.com>, linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, linux-mm@...ck.org,
virtio-dev@...ts.oasis-open.org, kvm@...r.kernel.org,
qemu-devel@...gnu.org, quintela@...hat.com, dgilbert@...hat.com,
pbonzini@...hat.com, cornelia.huck@...ibm.com, amit.shah@...hat.com
Subject: Re: [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast
(de)inflating & fast live migration
On Fri, Oct 21, 2016 at 10:25:21AM -0700, Dave Hansen wrote:
> On 10/20/2016 11:24 PM, Liang Li wrote:
> > Dave Hansen suggested a new scheme to encode the data structure,
> > because of additional complexity, it's not implemented in v3.
>
> So, what do you want done with this patch set? Do you want it applied
> as-is so that we can introduce a new host/guest ABI that we must support
> until the end of time? Then, we go back in a year or two and add the
> newer format that addresses the deficiencies that this ABI has with a
> third version?
>
Exactly my questions.
Powered by blists - more mailing lists