perf tools: Use cpu/possible instead of cpu/kernel_max

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>

diff --git a/tools/perf/util/cpumap.c b/tools/perf/util/cpumap.c
index 526da022b3c4aa653f53bc21046926fd6a4a08d8..c4e55b71010c6b52f2be7bc6c3af053c6f4183d0 100644 (file)
--- 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 */
-       ret = snprintf(path, PATH_MAX, "%s/devices/system/cpu/kernel_max", mnt);
+       ret = snprintf(path, PATH_MAX, "%s/devices/system/cpu/possible", mnt);
        if (ret == PATH_MAX) {
                pr_err("sysfs path crossed PATH_MAX(%d) size\n", PATH_MAX);
                goto out;