From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian.Jackson@eu.citrix.com, xen-devel@lists.xensource.com,
Wei Liu <wei.liu2@citrix.com>,
mlatimer@suse.com
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 [thread overview]
Message-ID: <1425905167.21353.31.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1503091240000.9880@kaball.uk.xensource.com>
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.
*/
next prev parent reply other threads:[~2015-03-09 12:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:16 [PATCH v2 0/4] fix freemem loop Stefano Stabellini
2015-03-06 17:19 ` [PATCH v2 1/4] Revert "libxl: Wait for ballooning if free memory is increasing" Stefano Stabellini
2015-03-09 11:15 ` Wei Liu
2015-03-09 11:26 ` Stefano Stabellini
2015-03-06 17:19 ` [PATCH v2 2/4] libxl_wait_for_memory_target: wait as long as dom0 is making progress Stefano Stabellini
2015-03-09 11:17 ` Wei Liu
2015-03-09 12:41 ` Stefano Stabellini
2015-03-09 12:46 ` Ian Campbell [this message]
2015-03-09 12:57 ` Wei Liu
2015-03-06 17:19 ` [PATCH v2 3/4] freemem: remove call to libxl_wait_for_free_memory Stefano Stabellini
2015-03-06 17:19 ` [PATCH v2 4/4] libxl_wait_for_memory_target: wait for 2 sec at a time Stefano Stabellini
2015-03-11 12:30 ` [PATCH v2 0/4] fix freemem loop Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1425905167.21353.31.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=mlatimer@suse.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.