From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933769AbcJURZY (ORCPT ); Fri, 21 Oct 2016 13:25:24 -0400 Received: from mga07.intel.com ([134.134.136.100]:62583 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932507AbcJURZW (ORCPT ); Fri, 21 Oct 2016 13:25:22 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,377,1473145200"; d="scan'208";a="22265748" Subject: Re: [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration To: Liang Li , mst@redhat.com References: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-mm@kvack.org, virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com, cornelia.huck@de.ibm.com, amit.shah@redhat.com From: Dave Hansen Message-ID: <580A4F81.60201@intel.com> Date: Fri, 21 Oct 2016 10:25:21 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0 MIME-Version: 1.0 In-Reply-To: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration Date: Fri, 21 Oct 2016 10:25:21 -0700 Message-ID: <580A4F81.60201@intel.com> References: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, amit.shah@redhat.com, qemu-devel@nongnu.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, pbonzini@redhat.com, virtualization@lists.linux-foundation.org, dgilbert@redhat.com To: Liang Li , mst@redhat.com Return-path: In-Reply-To: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org List-Id: kvm.vger.kernel.org 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? From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f197.google.com (mail-pf0-f197.google.com [209.85.192.197]) by kanga.kvack.org (Postfix) with ESMTP id AEEED6B0038 for ; Fri, 21 Oct 2016 13:25:22 -0400 (EDT) Received: by mail-pf0-f197.google.com with SMTP id 128so58325870pfz.1 for ; Fri, 21 Oct 2016 10:25:22 -0700 (PDT) Received: from mga14.intel.com (mga14.intel.com. [192.55.52.115]) by mx.google.com with ESMTPS id ae6si2906254pad.277.2016.10.21.10.25.21 for (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 21 Oct 2016 10:25:21 -0700 (PDT) Subject: Re: [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration References: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> From: Dave Hansen Message-ID: <580A4F81.60201@intel.com> Date: Fri, 21 Oct 2016 10:25:21 -0700 MIME-Version: 1.0 In-Reply-To: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Liang Li , mst@redhat.com Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-mm@kvack.org, virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com, cornelia.huck@de.ibm.com, amit.shah@redhat.com 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? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:48313) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bxdZP-0000el-1M for qemu-devel@nongnu.org; Fri, 21 Oct 2016 13:25:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bxdZL-00021G-UI for qemu-devel@nongnu.org; Fri, 21 Oct 2016 13:25:27 -0400 Received: from mga03.intel.com ([134.134.136.65]:47779) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1bxdZL-00020j-M2 for qemu-devel@nongnu.org; Fri, 21 Oct 2016 13:25:23 -0400 References: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> From: Dave Hansen Message-ID: <580A4F81.60201@intel.com> Date: Fri, 21 Oct 2016 10:25:21 -0700 MIME-Version: 1.0 In-Reply-To: <1477031080-12616-1-git-send-email-liang.z.li@intel.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RESEND PATCH v3 kernel 0/7] Extend virtio-balloon for fast (de)inflating & fast live migration List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Liang Li , mst@redhat.com Cc: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, linux-mm@kvack.org, virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org, qemu-devel@nongnu.org, quintela@redhat.com, dgilbert@redhat.com, pbonzini@redhat.com, cornelia.huck@de.ibm.com, amit.shah@redhat.com 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?