xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com, lccycc123@gmail.com,
	george.dunlap@eu.citrix.com, msw@linux.com,
	dario.faggioli@citrix.com, stefano.stabellini@eu.citrix.com,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v5 8/8] add vnuma info for debug-key
Date: Tue, 03 Jun 2014 10:04:05 +0100	[thread overview]
Message-ID: <538DABA50200007800017347@mail.emea.novell.com> (raw)
In-Reply-To: <1401771200-11448-2-git-send-email-ufimtseva@gmail.com>

>>> On 03.06.14 at 06:53, <ufimtseva@gmail.com> wrote:

This patch appears to be duplicated (with slightly different titles) in
the series - please fix this up for the next revision.

> --- a/xen/arch/x86/numa.c
> +++ b/xen/arch/x86/numa.c
> @@ -347,9 +347,10 @@ EXPORT_SYMBOL(node_data);
>  static void dump_numa(unsigned char key)
>  {
>  	s_time_t now = NOW();
> -	int i;
> +	int i, j, n, err;

"unsigned int" please for any variables used as array indexes or alike
and not explicitly needing to be signed for some reason.

>  	struct domain *d;
>  	struct page_info *page;
> +	char tmp[12];

Are you perhaps unaware of keyhandler_scratch[]?

>  	unsigned int page_num_node[MAX_NUMNODES];
>  
>  	printk("'%c' pressed -> dumping numa info (now-0x%X:%08X)\n", key,
> @@ -389,6 +390,32 @@ static void dump_numa(unsigned char key)
>  
>  		for_each_online_node(i)
>  			printk("    Node %u: %u\n", i, page_num_node[i]);
> +
> +		printk("    Domain has %u vnodes\n", d->vnuma.nr_vnodes);
> +		for ( i = 0; i < d->vnuma.nr_vnodes; i++ ) {
> +			err = snprintf(tmp, 12, "%u", d->vnuma.vnode_to_pnode[i]);
> +			if ( err < 0 )
> +				printk("        vnode %u - pnode %s,", i, "any");
> +			else
> +				printk("        vnode %u - pnode %s,", i,
> +			d->vnuma.vnode_to_pnode[i] == NUMA_NO_NODE ? "any" : tmp);

Broken indentation.

> +			printk(" %"PRIu64" MB, ",
> +				(d->vnuma.vmemrange[i].end - d->vnuma.vmemrange[i].start) >> 20);

Here too.

> +			printk("vcpus: ");
> +
> +			for ( j = 0, n = 0; j < d->max_vcpus; j++ ) {
> +				if ( d->vnuma.vcpu_to_vnode[j] == i ) {
> +					if ( !((n + 1) % 8) )
> +						printk("%u\n", j);
> +					else if ( !(n % 8) && n != 0 )
> +							printk("%s%u ", "             ", j);
> +						else
> +							printk("%u ", j);

And yet more of them. Also the sequence of leading spaces would better
be expressed with %8u or some such, but from the looks of it properly
aligning the output here would require all of this to be done a little
differently anyway.

Jan

  reply	other threads:[~2014-06-03  9:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-03  4:53 [PATCH v5 0/8] vnuma introduction Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 8/8] add vnuma info for debug-key Elena Ufimtseva
2014-06-03  9:04   ` Jan Beulich [this message]
2014-06-04  4:13     ` Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 1/8] xen: vnuma topoplogy and subop hypercalls Elena Ufimtseva
2014-06-03  8:55   ` Jan Beulich
2014-06-03  4:53 ` [PATCH v5 2/8] libxc: Plumb Xen with vnuma topology Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 3/8] vnuma xl.cfg.pod and idl config options Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 4/8] vnuma topology parsing routines Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 5/8] libxc: allocate domain vnuma nodes Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 6/8] libxl: build e820 map for vnodes Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 7/8] libxl: place vnuma domain nodes on numa nodes Elena Ufimtseva
2014-06-03  4:53 ` [PATCH v5 8/8] add vnuma info out on debug-key Elena Ufimtseva
2014-06-03 11:37 ` [PATCH v5 0/8] vnuma introduction Wei Liu
2014-06-04  4:05   ` Elena Ufimtseva

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=538DABA50200007800017347@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=lccycc123@gmail.com \
    --cc=msw@linux.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=ufimtseva@gmail.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).