From: Elena Ufimtseva <ufimtseva@gmail.com>
To: xen-devel@lists.xen.org
Cc: Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com,
george.dunlap@eu.citrix.com, msw@linux.com,
dario.faggioli@citrix.com, lccycc123@gmail.com,
ian.jackson@eu.citrix.com, Elena Ufimtseva <ufimtseva@gmail.com>
Subject: [PATCH v2 6/7] xen: adds vNUMA info debug-key u
Date: Wed, 13 Nov 2013 22:27:19 -0500 [thread overview]
Message-ID: <1384399639-24164-1-git-send-email-ufimtseva@gmail.com> (raw)
Prints basic information about vNUMA topology
for vNUMA enabled domains when issuing debug-key 'u'.
Signed-off-by: Elena Ufimtseva <ufimtseva@gmail.com>
---
xen/arch/x86/numa.c | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/xen/arch/x86/numa.c b/xen/arch/x86/numa.c
index b141877..8bd34d0 100644
--- a/xen/arch/x86/numa.c
+++ b/xen/arch/x86/numa.c
@@ -389,6 +389,25 @@ static void dump_numa(unsigned char key)
for_each_online_node(i)
printk(" Node %u: %u\n", i, page_num_node[i]);
+
+ if (d->vnuma.nr_vnodes > 0)
+ {
+ printk(" Domain has %d vnodes\n", d->vnuma.nr_vnodes);
+ for (i = 0; i < d->vnuma.nr_vnodes; i++) {
+ printk(" vnode %d - pnode %d:", i,
+ d->vnuma.vnode_numamap[i] >= MAX_NUMNODES ?
+ -1 : d->vnuma.vnode_numamap[i]);
+ printk(" %"PRIu64" MB \n",
+ (d->vnuma.vmemrange[i].end -
+ d->vnuma.vmemrange[i].start) >> 20);
+ }
+ printk(" Domain vcpu to vnode: \n");
+ for (i = 0; i < d->max_vcpus; i++)
+ printk("%s%d %s", i % 8 == 0 ? " " : "",
+ d->vnuma.vcpu_to_vnode[i],
+ (i + 1) % 8 == 0 ? "\n" : "");
+ printk("\n");
+ }
}
rcu_read_unlock(&domlist_read_lock);
--
1.7.10.4
next reply other threads:[~2013-11-14 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 3:27 Elena Ufimtseva [this message]
2013-11-15 8:52 ` [PATCH v2 6/7] xen: adds vNUMA info debug-key u Jan Beulich
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=1384399639-24164-1-git-send-email-ufimtseva@gmail.com \
--to=ufimtseva@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lccycc123@gmail.com \
--cc=msw@linux.com \
--cc=stefano.stabellini@eu.citrix.com \
--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 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).