From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, keir@xen.org, keir.xen@gmail.com
Cc: dan.magenheimer@oracle.com
Subject: [PATCH v10] claim and its friends for allocating multiple self-ballooning guests.
Date: Mon, 4 Mar 2013 12:47:08 -0500 [thread overview]
Message-ID: <1362419234-29446-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey,
Two of these patches (Dan's) have been posted in the past, but I took it upon
myself to expand them and address some of the concerns and also continue the
discussion around them. I believe most people have been roped in the email
conversation about this and know what these patches are for. The first patch
(mmu: Introduce XENMEM_claim_pages (subop of memory ops) has a good blurb
about the problem/solution/alternative solutions.
The patches follow the normal code-flow - the patch to implement the two hypercalls:
XENMEM_claim_pages and XENMEM_get_unclaimed_pages.
Then the patches to utilize them in the libxc. The hypercall's are only utilized
if the toolstack (libxl) sets the claim_mode to anything but zero.
Then the toolstack (libxl + xl) patches. They revolve around two different changes:
1). Add 'claim_mode=[off|on|tmem]' global configuration value that determines
whether the claim hypercall should be used as part of guest creation.
2). Add an extra parameter -c to the 'xl info' to provide the output of how many
pages are claimed by different guests. This is more of a diagnostic patch.
That is it.
Dan Magenheimer (3):
mmu: Introduce XENMEM_claim_pages (subop of memory ops).
xc: use XENMEM_claim_pages during guest creation.
xc: XENMEM_claim_pages claimed but not possesed value.
Konrad Rzeszutek Wilk (3):
xl: Implement XENMEM_claim_pages support via 'claim_mode' global config
xl: export 'unclaimed_pages' value from xcinfo
xl: 'xl list' supports '-c' for global claim information.
docs/man/xl.conf.pod.5 | 30 ++++++++++
tools/examples/xl.conf | 5 ++
tools/libxc/xc_dom.h | 1 +
tools/libxc/xc_dom_x86.c | 12 ++++
tools/libxc/xc_domain.c | 26 +++++++++
tools/libxc/xc_hvm_build_x86.c | 17 ++++++
tools/libxc/xenctrl.h | 8 +++
tools/libxc/xenguest.h | 2 +
tools/libxl/libxl.c | 18 ++++++
tools/libxl/libxl.h | 3 +
tools/libxl/libxl_dom.c | 3 +-
tools/libxl/libxl_types.idl | 13 ++++-
tools/libxl/xl.c | 5 ++
tools/libxl/xl.h | 1 +
tools/libxl/xl_cmdimpl.c | 34 +++++++++--
tools/libxl/xl_cmdtable.c | 4 +-
tools/libxl/xl_sxp.c | 1 +
xen/common/domain.c | 1 +
xen/common/domctl.c | 1 +
xen/common/memory.c | 31 ++++++++++
xen/common/page_alloc.c | 126 ++++++++++++++++++++++++++++++++++++++++-
xen/include/public/domctl.h | 3 +-
xen/include/public/memory.h | 47 ++++++++++++++-
xen/include/xen/mm.h | 4 ++
xen/include/xen/sched.h | 1 +
25 files changed, 385 insertions(+), 12 deletions(-)
next reply other threads:[~2013-03-04 17:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 17:47 Konrad Rzeszutek Wilk [this message]
2013-03-04 17:47 ` [PATCH 1/6] mmu: Introduce XENMEM_claim_pages (subop of memory ops) Konrad Rzeszutek Wilk
2013-03-04 21:50 ` Keir Fraser
2013-03-05 12:01 ` Tim Deegan
2013-03-05 21:43 ` Konrad Rzeszutek Wilk
2013-03-06 9:07 ` Tim Deegan
2013-03-06 15:36 ` Konrad Rzeszutek Wilk
2013-03-07 14:59 ` Konrad Rzeszutek Wilk
2013-03-07 15:56 ` Tim Deegan
2013-03-08 20:07 ` Konrad Rzeszutek Wilk
2013-03-11 9:25 ` Tim Deegan
2013-03-04 17:47 ` [PATCH 2/6] xc: use XENMEM_claim_pages during guest creation Konrad Rzeszutek Wilk
2013-03-04 17:47 ` [PATCH 3/6] xl: Implement XENMEM_claim_pages support via 'claim_mode' global config Konrad Rzeszutek Wilk
2013-03-04 17:47 ` [PATCH 4/6] xc: XENMEM_claim_pages claimed but not possesed value Konrad Rzeszutek Wilk
2013-03-04 17:47 ` [PATCH 5/6] xl: export 'unclaimed_pages' value from xcinfo Konrad Rzeszutek Wilk
2013-03-04 17:47 ` [PATCH 6/6] xl: 'xl list' supports '-c' for global claim information Konrad Rzeszutek Wilk
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=1362419234-29446-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=keir.xen@gmail.com \
--cc=keir@xen.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).