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 5/6] xl: export 'outstanding_pages' value from xcinfo
Date: Fri, 29 Mar 2013 16:07:20 -0400	[thread overview]
Message-ID: <20130329200720.GA6467@phenom.dumpdata.com> (raw)
In-Reply-To: <20820.29542.207528.170395@mariner.uk.xensource.com>

On Thu, Mar 28, 2013 at 04:44:22PM +0000, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("[PATCH 5/6] xl: export 'outstanding_pages' value from xcinfo"):
> > This patch provides the value of the currently outstanding pages
> > claimed for a specific domain. This is a value that influences
> > the global outstanding claims value (See patch: "xl: 'xl info'
> > print outstanding claims if enabled") returned via
> > xc_domain_get_outstanding_pages hypercall. This domain value
> > decrements as the memory is populated for the guest and
> > eventually reaches zero.
> 
> Again this patch is fine as far as it goes but we need an update to
> the documentation with a clear and accurate definition of what these
> values are.

The original patch (v11) had this outputed to SXP but as that is in the
'do-not-touch' that part had to be removed.

And the 'libxl_dominfo' structure that comes out of this change, is only
consumed in couple of places and only certain attributes:

 - domid in 'list_domains_details'.
 - domid, vcpu_online, blocked, paused, shutdown, dying, cpu_time, ssidref in 'list_domains'.
 - vcpu_online in 'main_cpupoolnumasplit'.
 - current_memkb, shared_memkb, domid, shutdown in 'sharing'.

Nobody seems to be using 'page_memkb', nor 'vcpu_max_id'.

I could provide the 'outstanding_memkb' value as part of 'list_domains'
but that would alter the existing format it has. I could create an 'xl claim' that would
be similar to 'xl list' but also include the claim information. 

But I am not sure whether there is a need for it. The 'outstanding_claims' via (xl info)
is good enough for it.

So your call - My thinking was that this could be in the code to be potentially
used in the future (hand-waving how), but I am also OK with just dropping this
patch and the earlier: xl/xc: export outstanding_pages value in xc_dominfo structure.

Let me actually drop it from the next posting - it is always nicer to have a slimmed
down version of patchsets.

  reply	other threads:[~2013-03-29 20:07 UTC|newest]

Thread overview: 26+ 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 [this message]
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
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
  -- strict thread matches above, loose matches on Subject: below --
2013-04-10 19:59 [PATCH v15] " Konrad Rzeszutek Wilk
2013-04-10 19:59 ` [PATCH 5/6] xl: export 'outstanding_pages' value from xcinfo Konrad Rzeszutek Wilk
2013-04-12 15:19   ` Ian Jackson
2013-03-11 14:20 [PATCH v11] claim and its friends for allocating multiple self-ballooning guests Konrad Rzeszutek Wilk
2013-03-11 14:20 ` [PATCH 5/6] xl: export 'outstanding_pages' value from xcinfo Konrad Rzeszutek Wilk
2013-03-13 10:44   ` 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=20130329200720.GA6467@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.