All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH 6/6] xl: 'xl info' print outstanding claims if enabled (claim_mode=1 in xl.conf)
Date: Fri, 29 Mar 2013 09:31:14 -0400	[thread overview]
Message-ID: <20130329133114.GF31356@phenom.dumpdata.com> (raw)
In-Reply-To: <20820.29717.491712.538567@mariner.uk.xensource.com>

On Thu, Mar 28, 2013 at 04:47:17PM +0000, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("[PATCH 6/6] xl: 'xl info' print outstanding claims if enabled (claim_mode=1 in xl.conf)"):
> > This patch provides the value of the currently outstanding pages
> > claimed for all domains. This is a total global value that influences
> > the hypervisors' MM system.
> > 
> > When a claim call is done, a reservation for a specific amount of pages
> > is set and also a global value is incremented. This global value is then
> > reduced as the domain's memory is populated and eventually reaches zero.
> > The toolstack can also choose to set the domain's claim to zero which
> > cancels the reservation and decrements the global value by the amount
> > of claim that has not been satisfied.
> 
> This description is good, but something like it needs to be in the
> documentation.

The documentation being xl.conf right? It already is in xen.conf thanks
to the first patch.

> 
> > +uint64_t libxl_get_claiminfo(libxl_ctx *ctx)
> > +{
> > +    long l;
> > +
> > +    l = xc_domain_get_outstanding_pages(ctx->xch);
> > +    if (l < 0)
> > +        return l;
> > +
> > +    /* In MB */
> > +    return (l >> 8);
> > +}
> 
> libxl functions should return libxl error values, not whatever you got
> from libxc.

OK.
> 
> I don't mind very much what the libxc function returns but the libxl
> function needs to handle the error properly.  See Ian C's comments on
> the previous version of this patch.

OK, I probably missed something in his reply - the errno that we would
mostly get (-ENOSYS) is neutered, so that it would not pipe up to
libxl (first patch).

However, there is of course nothing stopping from adding better error
handling in this code in case we get -EPERM or such. Patch shortly coming up.

> 
> Thanks,
> Ian.

  reply	other threads:[~2013-03-29 13:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 20:55 [PATCH v13] claim and its friends for allocating multiple self-ballooning guests Konrad Rzeszutek Wilk
2013-03-27 20:55 ` [PATCH 1/6] xc: use XENMEM_claim_pages hypercall during guest creation Konrad Rzeszutek Wilk
2013-03-28 16:23   ` Ian Jackson
2013-03-29 13:12     ` Konrad Rzeszutek Wilk
2013-03-27 20:55 ` [PATCH 2/6] xl: Implement XENMEM_claim_pages support via 'claim_mode' global config Konrad Rzeszutek Wilk
2013-03-28 16:39   ` Ian Jackson
2013-03-29 19:30     ` Konrad Rzeszutek Wilk
2013-03-27 20:55 ` [PATCH 3/6] xend: Implement XENMEM_claim_pages support via 'claim-mode' " Konrad Rzeszutek Wilk
2013-03-28 16:41   ` Ian Jackson
2013-03-29 13:27     ` Konrad Rzeszutek Wilk
2013-03-29 20:17       ` Konrad Rzeszutek Wilk
2013-03-27 20:55 ` [PATCH 4/6] xc: export outstanding_pages value in xc_dominfo structure Konrad Rzeszutek Wilk
2013-03-28 16:43   ` Ian Jackson
2013-03-27 20:55 ` [PATCH 5/6] xl: export 'outstanding_pages' value from xcinfo Konrad Rzeszutek Wilk
2013-03-28 16:44   ` Ian Jackson
2013-03-29 20:07     ` Konrad Rzeszutek Wilk
2013-03-27 20:55 ` [PATCH 6/6] xl: 'xl info' print outstanding claims if enabled (claim_mode=1 in xl.conf) Konrad Rzeszutek Wilk
2013-03-28 16:47   ` Ian Jackson
2013-03-29 13:31     ` Konrad Rzeszutek Wilk [this message]
2013-03-28 16:17 ` [PATCH v13] claim and its friends for allocating multiple self-ballooning guests Ian Jackson
2013-03-28 16:50 ` Ian Jackson
2013-04-02 11:10   ` George Dunlap

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=20130329133114.GF31356@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dan.magenheimer@oracle.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.