From: Jiri Olsa <jolsa@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Don Zickus <dzickus@redhat.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: [PATCH 3/5] perf tools: Use cpu/possible instead of cpu/kernel_max
Date: Fri, 18 Apr 2014 12:31:57 +0200 [thread overview]
Message-ID: <1397817119-15195-4-git-send-email-jolsa@redhat.com> (raw)
In-Reply-To: <1397817119-15195-1-git-send-email-jolsa@redhat.com>
From: Don Zickus <dzickus@redhat.com>
The system's max configuration is represented by cpu/possible and
cpu/kernel_max can be huge (4096 vs. 128), so save space by keeping
smaller structures.
Signed-off-by: Don Zickus <dzickus@redhat.com>
Reviewed-by: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/r/1396896924-129847-3-git-send-email-dzickus@redhat.com
Signed-off-by: Jiri Olsa <jolsa@redhat.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 0a27732..3d124fb 100644
--- a/tools/perf/util/cpumap.c
+++ b/tools/perf/util/cpumap.c
@@ -365,7 +365,7 @@ static void set_max_cpu_num(void)
goto out;
/* get the highest possible cpu number for a sparse allocation */
- snprintf(path, PATH_MAX, "%s/devices/system/cpu/kernel_max", mnt);
+ snprintf(path, PATH_MAX, "%s/devices/system/cpu/possible", mnt);
ret = get_max_num(path, &max_cpu_num);
--
1.8.3.1
next prev parent reply other threads:[~2014-04-18 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 10:31 [GIT PULL 0/5] perf/core improvements and fixes Jiri Olsa
2014-04-18 10:31 ` [PATCH 1/5] perf tools: Fix pmu object compilation error Jiri Olsa
2014-04-18 10:31 ` [PATCH 2/5] perf tools: Allow ability to map cpus to nodes easily Jiri Olsa
2014-04-18 10:31 ` Jiri Olsa [this message]
2014-04-18 10:31 ` [PATCH 4/5] perf kmem: Utilize the new generic cpunode_map Jiri Olsa
2014-04-18 10:31 ` [PATCH 5/5] perf callchain: Add generic report parse callchain callback function Jiri Olsa
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=1397817119-15195-4-git-send-email-jolsa@redhat.com \
--to=jolsa@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
all inboxes | Powered by JetHome®