From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Liu Subject: [PATCH 0/2] Revert changes to libxl_set_memory_target, unblock 4.6 Date: Tue, 23 Jun 2015 15:16:22 +0100 Message-ID: <1435068984-9163-1-git-send-email-wei.liu2@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z7P1x-00056H-Bg for xen-devel@lists.xenproject.org; Tue, 23 Jun 2015 14:18:29 +0000 List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Xen-devel Cc: Wei Liu , Ian Campbell , Stefano Stabellini , George Dunlap , Andrew Cooper , Ian Jackson List-Id: xen-devel@lists.xenproject.org A new memory model that allows QEMU to bump memory behind libxl's back was merged a few months ago. We didn't fully understand the repercussions back then. Now it breaks migration and becomes blocker of 4.6 release. It's better to restore to original behaviour at this stage of the release cycle, that would put us in a position no worse than before, so the release is unblocked. The said function is still racy after reverting these two patches. Making domain memory state consistent requires a bit more work. Separate patch(es) will be sent out to deal with that problem. Wei. Wei Liu (2): Revert "libxl: fix "xl mem-set" regression from 0c029c4da2" Revert "libxl_set_memory_target: retain the same maxmem offset on top of the current target" tools/libxc/include/xenctrl.h | 2 +- tools/libxc/xc_domain.c | 2 +- tools/libxl/libxl.c | 29 ++++++++++++++++------------- 3 files changed, 18 insertions(+), 15 deletions(-) -- 1.9.1