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: Fri, 1 Mar 2019 11:26:44 +0100 [thread overview]
Message-ID: <20190301102644.GC2979@krava> (raw)
In-Reply-To: <9ee9ca23-bb29-2038-5fe3-d52bcf4cd049@linux.ibm.com>
On Fri, Mar 01, 2019 at 12:35:39PM +0530, Ravi Bangoria wrote:
>
> On 2/28/19 9:52 PM, Jiri Olsa wrote:
> > how about attached change (untested)?
>
> LGTM. Would you mind sending a patch.
attached, please test on your system
thanks,
jirka
---
Ravi Bangoria reported that we fail with empty
numa node with following message:
$ lscpu
NUMA node0 CPU(s):
NUMA node1 CPU(s): 0-4
$ sudo ./perf c2c report
node/cpu topology bugFailed setup nodes
Fixing this by detecting empty node and keeping
its cpu set empty.
Reported-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Link: http://lkml.kernel.org/n/tip-dyq5jo6pn1j3yqavb5ukjwwu@git.kernel.org
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
---
tools/perf/builtin-c2c.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/tools/perf/builtin-c2c.c b/tools/perf/builtin-c2c.c
index 4272763a5e96..9e6cc868bdb4 100644
--- a/tools/perf/builtin-c2c.c
+++ b/tools/perf/builtin-c2c.c
@@ -2056,6 +2056,12 @@ static int setup_nodes(struct perf_session *session)
if (!set)
return -ENOMEM;
+ nodes[node] = set;
+
+ /* empty node, skip */
+ if (cpu_map__empty(map))
+ continue;
+
for (cpu = 0; cpu < map->nr; cpu++) {
set_bit(map->map[cpu], set);
@@ -2064,8 +2070,6 @@ static int setup_nodes(struct perf_session *session)
cpu2node[map->map[cpu]] = node;
}
-
- nodes[node] = set;
}
setup_nodes_header();
--
2.17.2
next prev parent reply other threads:[~2019-03-01 10:26 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
2019-02-28 16:22 ` Jiri Olsa
2019-03-01 7:05 ` Ravi Bangoria
2019-03-01 10:26 ` Jiri Olsa [this message]
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=20190301102644.GC2979@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 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.