From: Jason Baron <jbaron@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: fweisbec@gmail.com, mingo@elte.hu, laijs@cn.fujitsu.com,
rostedt@goodmis.org, peterz@infradead.org,
mathieu.desnoyers@polymtl.ca, jiayingz@google.com,
mbligh@google.com, roland@redhat.com, fche@redhat.com,
lizf@cn.fujitsu.com
Subject: [PATCH 5/7] V2 add syscall tracepoints
Date: Tue, 23 Jun 2009 14:29:10 -0400 [thread overview]
Message-ID: <4ad00d330cce7b026185153913e0971a1bbb4dee.1245770664.git.jbaron@redhat.com> (raw)
In-Reply-To: <cover.1245770664.git.jbaron@redhat.com>
update FTRACE_SYSCALL_MAX to the current number of syscalls
Signed-off-by: Jason Baron <jbaron@redhat.com>
Acked-by: Frederic Weisbecker <fweisbec@gmail.com>
---
arch/x86/include/asm/ftrace.h | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/ftrace.h b/arch/x86/include/asm/ftrace.h
index bd2c651..d16d195 100644
--- a/arch/x86/include/asm/ftrace.h
+++ b/arch/x86/include/asm/ftrace.h
@@ -30,9 +30,9 @@
/* FIXME: I don't want to stay hardcoded */
#ifdef CONFIG_X86_64
-# define FTRACE_SYSCALL_MAX 296
+# define FTRACE_SYSCALL_MAX 298
#else
-# define FTRACE_SYSCALL_MAX 333
+# define FTRACE_SYSCALL_MAX 336
#endif
#ifdef CONFIG_FUNCTION_TRACER
--
1.6.0.6
next prev parent reply other threads:[~2009-06-23 18:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 18:28 [PATCH 0/7] " Jason Baron
2009-06-23 18:28 ` [PATCH 1/7] " Jason Baron
2009-06-23 18:29 ` [PATCH 2/7] " Jason Baron
2009-06-23 18:29 ` [PATCH 3/7] " Jason Baron
2009-06-25 2:20 ` Li Zefan
2009-06-25 4:47 ` Frederic Weisbecker
2009-06-23 18:29 ` [PATCH 4/7] " Jason Baron
2009-06-25 2:21 ` Li Zefan
2009-06-23 18:29 ` Jason Baron [this message]
2009-06-23 18:29 ` [PATCH 6/7] " Jason Baron
2009-06-25 2:31 ` Li Zefan
2009-06-23 18:29 ` [PATCH 7/7] " Jason Baron
2009-06-25 2:38 ` Li Zefan
2009-06-25 1:27 ` [PATCH 0/7] " Li Zefan
2009-06-25 2:20 ` Li Zefan
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=4ad00d330cce7b026185153913e0971a1bbb4dee.1245770664.git.jbaron@redhat.com \
--to=jbaron@redhat.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jiayingz@google.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.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®