public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
	namhyung@kernel.org, eranian@google.com,
	linux-kernel@vger.kernel.org, tonyj@suse.com,
	nasastry@in.ibm.com
Subject: Re: [PATCH] perf c2c: Fix c2c report for empty numa node
Date: Thu, 28 Feb 2019 17:12:31 +0100	[thread overview]
Message-ID: <20190228161231.GB8674@krava> (raw)
In-Reply-To: <20190228153719.23411-1-ravi.bangoria@linux.ibm.com>

On Thu, Feb 28, 2019 at 09:07:19PM +0530, Ravi Bangoria wrote:
> perf c2c report fails if system has empty numa node(0 cpus):
> 
>   $ lscpu
>   NUMA node0 CPU(s):   
>   NUMA node1 CPU(s):   0-4
> 
>   $ sudo ./perf c2c report 
>   node/cpu topology bugFailed setup nodes
> 
> Fix this.
> 
> Reported-by: Nageswara R Sastry <nasastry@in.ibm.com>
> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
> ---
>  tools/perf/util/cpumap.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/perf/util/cpumap.c b/tools/perf/util/cpumap.c
> index 383674f448fc..517c3f37c613 100644
> --- a/tools/perf/util/cpumap.c
> +++ b/tools/perf/util/cpumap.c
> @@ -261,7 +261,7 @@ struct cpu_map *cpu_map__dummy_new(void)
>  	struct cpu_map *cpus = malloc(sizeof(*cpus) + sizeof(int));
>  
>  	if (cpus != NULL) {
> -		cpus->nr = 1;
> +		cpus->nr = 0;

you can't do this, there's one item in the map, nr needs to
reflect that.. it breaks 'perf test' badly

so the node is empty.. we need to teach c2c to work with that
I'll check

jirka

>  		cpus->map[0] = -1;
>  		refcount_set(&cpus->refcnt, 1);
>  	}
> -- 
> 2.17.1
> 

  reply	other threads:[~2019-02-28 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-28 15:37 [PATCH] perf c2c: Fix c2c report for empty numa node Ravi Bangoria
2019-02-28 16:12 ` Jiri Olsa [this message]
2019-02-28 16:22   ` Jiri Olsa
2019-03-01  7:05     ` Ravi Bangoria
2019-03-01 10:26       ` Jiri Olsa
2019-03-02  3:07         ` Ravi Bangoria

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=20190228161231.GB8674@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=nasastry@in.ibm.com \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=tonyj@suse.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