From: Andres Lagar-Cavilla <andres@lagarcavilla.org>
To: xen-devel@lists.xen.org
Cc: ian.campbell@citrix.com, andres@gridcentric.ca, tim@xen.org,
keir.xen@gmail.com, JBeulich@suse.com, ian.jackson@citrix.com,
adin@gridcentric.ca
Subject: [PATCH 1 of 2] Propagate domain shared pages via dominfo
Date: Mon, 12 Mar 2012 15:53:27 -0400 [thread overview]
Message-ID: <94ec84eeca5d90e983e8.1331582007@xdev.gridcentric.ca> (raw)
In-Reply-To: <patchbomb.1331582006@xdev.gridcentric.ca>
tools/libxc/xc_domain.c | 2 +-
xen/common/domctl.c | 2 +-
xen/include/public/domctl.h | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
Currently commented out, no reason to disable it.
Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
diff -r addb6616e282 -r 94ec84eeca5d tools/libxc/xc_domain.c
--- a/tools/libxc/xc_domain.c
+++ b/tools/libxc/xc_domain.c
@@ -234,7 +234,7 @@ int xc_domain_getinfo(xc_interface *xch,
info->ssidref = domctl.u.getdomaininfo.ssidref;
info->nr_pages = domctl.u.getdomaininfo.tot_pages;
- /* info->nr_shared_pages = domctl.u.getdomaininfo.shr_pages; */
+ info->nr_shared_pages = domctl.u.getdomaininfo.shr_pages;
info->nr_paged_pages = domctl.u.getdomaininfo.paged_pages;
info->max_memkb = domctl.u.getdomaininfo.max_pages << (PAGE_SHIFT-10);
info->shared_info_frame = domctl.u.getdomaininfo.shared_info_frame;
diff -r addb6616e282 -r 94ec84eeca5d xen/common/domctl.c
--- a/xen/common/domctl.c
+++ b/xen/common/domctl.c
@@ -153,7 +153,7 @@ void getdomaininfo(struct domain *d, str
info->tot_pages = d->tot_pages;
info->max_pages = d->max_pages;
- /* info->shr_pages = atomic_read(&d->shr_pages); */
+ info->shr_pages = atomic_read(&d->shr_pages);
info->paged_pages = atomic_read(&d->paged_pages);
info->shared_info_frame = mfn_to_gmfn(d, __pa(d->shared_info)>>PAGE_SHIFT);
BUG_ON(SHARED_M2P(info->shared_info_frame));
diff -r addb6616e282 -r 94ec84eeca5d xen/include/public/domctl.h
--- a/xen/include/public/domctl.h
+++ b/xen/include/public/domctl.h
@@ -94,7 +94,7 @@ struct xen_domctl_getdomaininfo {
uint32_t flags; /* XEN_DOMINF_* */
uint64_aligned_t tot_pages;
uint64_aligned_t max_pages;
- /* uint64_aligned_t shr_pages; */
+ uint64_aligned_t shr_pages;
uint64_aligned_t paged_pages;
uint64_aligned_t shared_info_frame; /* GMFN of shared_info struct */
uint64_aligned_t cpu_time;
next prev parent reply other threads:[~2012-03-12 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 19:53 [PATCH 0 of 2] Propagate sharing and paging counts to libx{c/l} Andres Lagar-Cavilla
2012-03-12 19:53 ` Andres Lagar-Cavilla [this message]
2012-03-13 10:41 ` [PATCH 1 of 2] Propagate domain shared pages via dominfo Ian Campbell
2012-03-12 19:53 ` [PATCH 2 of 2] libxl: publish number of shared and paged pages Andres Lagar-Cavilla
2012-03-13 10:42 ` Ian Campbell
2012-03-13 14:14 ` Andres Lagar-Cavilla
2012-03-13 14:32 ` Ian Campbell
2012-03-13 14:40 ` Andres Lagar-Cavilla
2012-03-13 15:35 ` Ian Jackson
2012-03-13 15:40 ` Ian Campbell
2012-03-13 15:43 ` Ian Jackson
2012-03-13 15:52 ` Ian Campbell
2012-03-13 16:08 ` Ian Jackson
2012-03-13 15:43 ` Andres Lagar-Cavilla
2012-03-13 15:35 ` Ian Jackson
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=94ec84eeca5d90e983e8.1331582007@xdev.gridcentric.ca \
--to=andres@lagarcavilla.org \
--cc=JBeulich@suse.com \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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.