Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965557AbdCYBdf (ORCPT ); Fri, 24 Mar 2017 21:33:35 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:32838 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756459AbdCYBd0 (ORCPT ); Fri, 24 Mar 2017 21:33:26 -0400 Subject: Re: maybe revert commit c275a57f5ec3 "xen/balloon: Set balloon's initial state to number of existing RAM pages" To: Dan Streetman , Konrad Rzeszutek Wilk References: <0628e2af-f7e7-056a-82ec-68860f9c4f29@oracle.com> <20170324211016.GG9755@char.us.oracle.com> Cc: Juergen Gross , xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org From: Boris Ostrovsky Message-ID: Date: Fri, 24 Mar 2017 21:33:07 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Source-IP: aserv0022.oracle.com [141.146.126.234] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 386 Lines: 13 > > I think we can all agree that the *ideal* situation would be, for the > balloon driver to not immediately hotplug memory so it can add 11 more > pages, so maybe I just need to figure out why the balloon driver > thinks it needs 11 more pages, and fix that. How does the new memory appear in the guest? Via online_pages()? Or is ballooning triggered from watch_target()? -boris