From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [PATCH v2 2/4] libxl_wait_for_memory_target: wait as long as dom0 is making progress Date: Mon, 9 Mar 2015 12:46:07 +0000 Message-ID: <1425905167.21353.31.camel@citrix.com> References: <1425662357-9951-2-git-send-email-stefano.stabellini@eu.citrix.com> <20150309111719.GN18491@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: Ian.Jackson@eu.citrix.com, xen-devel@lists.xensource.com, Wei Liu , mlatimer@suse.com List-Id: xen-devel@lists.xenproject.org On Mon, 2015-03-09 at 12:41 +0000, Stefano Stabellini wrote: > Given the very limited change in behaviour (in fact existing callers > should work as-is) I thought that we could do without one. Also see: > http://marc.info/?l=xen-devel&m=142563879603876&w=2. I was also basing that on the big comment above this section which reads: /* * WARNING * This memory management API is unstable even in Xen 4.2. * It has a numer of deficiencies and we intend to replace it. * * The semantics of these functions should not be relied on to be very * coherent or stable. We will however endeavour to keep working * existing programs which use them in roughly the same way as libxl. */