From: tip-bot for David Ahern <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, david.ahern@oracle.com, hpa@zytor.com,
tglx@linutronix.de, acme@redhat.com,
linux-kernel@vger.kernel.org
Subject: [tip:perf/core] perf: Bump max number of cpus to 1024
Date: Fri, 27 Mar 2015 00:40:18 -0700 [thread overview]
Message-ID: <tip-4d255766d28b1fecec7e00ab4166b2c17bfc37be@git.kernel.org> (raw)
In-Reply-To: <1427213438-127216-1-git-send-email-david.ahern@oracle.com>
Commit-ID: 4d255766d28b1fecec7e00ab4166b2c17bfc37be
Gitweb: http://git.kernel.org/tip/4d255766d28b1fecec7e00ab4166b2c17bfc37be
Author: David Ahern <david.ahern@oracle.com>
AuthorDate: Tue, 24 Mar 2015 12:10:38 -0400
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Thu, 26 Mar 2015 10:52:28 -0300
perf: Bump max number of cpus to 1024
SPARC based systems currently support up to 1024 cpus (e.g. T5-8).
Allow perf to work on those systems.
Signed-off-by: David Ahern <david.ahern@oracle.com>
Link: http://lkml.kernel.org/r/1427213438-127216-1-git-send-email-david.ahern@oracle.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/perf.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/perf.h b/tools/perf/perf.h
index 1caa70a..c38a085 100644
--- a/tools/perf/perf.h
+++ b/tools/perf/perf.h
@@ -29,7 +29,7 @@ static inline unsigned long long rdclock(void)
return ts.tv_sec * 1000000000ULL + ts.tv_nsec;
}
-#define MAX_NR_CPUS 256
+#define MAX_NR_CPUS 1024
extern const char *input_name;
extern bool perf_host, perf_guest;
prev parent reply other threads:[~2015-03-27 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:10 [PATCH] perf: Bump max number of cpus to 1024 David Ahern
2015-03-24 16:21 ` Arnaldo Carvalho de Melo
2015-03-27 7:40 ` tip-bot for David Ahern [this message]
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=tip-4d255766d28b1fecec7e00ab4166b2c17bfc37be@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=david.ahern@oracle.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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.