From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question about four kinds of pages in struct xc_dominfo
Date: Fri, 3 Jan 2014 13:49:44 -0500 [thread overview]
Message-ID: <20140103184944.GB29402@phenom.dumpdata.com> (raw)
In-Reply-To: <CAENZ-+=v4TyP4_VxoU6B_w90gVZPhMkk7Yv0mKPYBF-po0y6xA@mail.gmail.com>
On Tue, Dec 31, 2013 at 04:43:55PM -0500, Meng Xu wrote:
> Hi,
>
> I'm trying to print out the "current used" pages of each domU.
>
> I'm reading the xen code and found the data structure xc_dominfo at file
> tools/libxc/xenctrl.h.
>
> *I have a simple, maybe very naive question: *
> 1) What is the difference among *nr_outstanding_pages*, * nr_shared_pages*,
> and *nr_paged_pages*?
The nr_outstanding_pages is usually zero. It means the amount of
pages that are needed for the guest to be allocated.
The nr_shared_pages - is the number of pages that are shared with other
guests or tools
The nr_ages_pages - that is if you page the pages to swap of a VM.
You need to use xenpaging for that.
> 2) Could anyone point me to a place that I can find the document of the
> definition of the structures in xen code, so that I can find those
> definition by myself?
Um, I usually use 'git annotate' on the file and the commit description
gives me a good idea
>
> I'm new to the xen source and hope you can give me some guide to hack the
> xen code.
>
> ========The structure is as below======================
> "tools/libxc/xenctrl.h"
> /*
> * DOMAIN MANAGEMENT FUNCTIONS
> */
>
> typedef struct xc_dominfo {
> uint32_t domid;
> uint32_t ssidref;
> unsigned int dying:1, crashed:1, shutdown:1,
> paused:1, blocked:1, running:1,
> hvm:1, debugged:1;
> unsigned int shutdown_reason; /* only meaningful if shutdown==1 */
> unsigned long nr_pages; /* current number, not maximum */
> unsigned long nr_outstanding_pages;
> unsigned long nr_shared_pages;
> unsigned long nr_paged_pages;
> unsigned long shared_info_frame;
> uint64_t cpu_time;
> unsigned long max_memkb;
> unsigned int nr_online_vcpus;
> unsigned int max_vcpu_id;
> xen_domain_handle_t handle;
> unsigned int cpupool;
> } xc_dominfo_t;
>
>
> Thank you very much for your time and help in these questions!
> Happy New Year!
You too!
>
> Best,
>
> Meng
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-01-03 18:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 21:43 Question about four kinds of pages in struct xc_dominfo Meng Xu
2014-01-03 18:49 ` Konrad Rzeszutek Wilk [this message]
2014-01-03 20:17 ` Meng Xu
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=20140103184944.GB29402@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.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.