public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
	laijs@cn.fujitsu.com, rostedt@goodmis.org, peterz@infradead.org,
	mathieu.desnoyers@polymtl.ca, jiayingz@google.com,
	bligh@google.com, roland@redhat.com, fche@redhat.com
Subject: Re: [PATCH 5/7] add syscall tracepoints
Date: Fri, 19 Jun 2009 04:14:18 +0200	[thread overview]
Message-ID: <20090619021418.GC7903@nowhere> (raw)
In-Reply-To: <51b4e9aff767dac4933ebb7835dee7068b158db8.1244837725.git.jbaron@redhat.com>

On Fri, Jun 12, 2009 at 05:24:59PM -0400, Jason Baron wrote:
> update FTRACE_SYSCALL_MAX to the current number of syscalls
> 
> 
> Signed-off-by: Jason Baron <jbaron@redhat.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 */


BTW, is there a way to know this size dynamically?
Or is there already a hardcoded number of syscalls somewhere
in x86?

Frederic.


>  #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
> 


  reply	other threads:[~2009-06-19  2:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 21:24 [PATCH 0/7] add syscall tracepoints Jason Baron
2009-06-12 21:24 ` [PATCH 1/7] " Jason Baron
2009-06-19  8:22   ` Li Zefan
2009-06-12 21:24 ` [PATCH 2/7] " Jason Baron
2009-06-19  3:24   ` Steven Rostedt
2009-06-19  8:26   ` Li Zefan
2009-06-12 21:24 ` [PATCH 3/7] " Jason Baron
2009-06-12 21:57   ` Mathieu Desnoyers
2009-06-15 14:12     ` Jason Baron
2009-06-15 15:24       ` Mathieu Desnoyers
2009-06-15 15:37         ` Frederic Weisbecker
2009-06-15 15:47           ` Mathieu Desnoyers
2009-06-19  1:59   ` Frederic Weisbecker
2009-06-19  3:29     ` Steven Rostedt
2009-06-19  3:40       ` Frederic Weisbecker
2009-06-12 21:24 ` [PATCH 4/7] " Jason Baron
2009-06-19  2:12   ` Frederic Weisbecker
2009-06-19 12:35     ` Mathieu Desnoyers
2009-06-19 14:56       ` Frederic Weisbecker
2009-06-19  8:31   ` Li Zefan
2009-06-12 21:24 ` [PATCH 5/7] " Jason Baron
2009-06-19  2:14   ` Frederic Weisbecker [this message]
2009-06-19  3:14     ` Li Zefan
2009-06-19  3:32       ` Steven Rostedt
2009-06-19  3:33       ` Frederic Weisbecker
2009-06-12 21:25 ` [PATCH 6/7] " Jason Baron
2009-06-19  2:28   ` Frederic Weisbecker
2009-06-19 21:49     ` Jason Baron
2009-06-12 21:25 ` [PATCH 7/7] " Jason Baron
2009-06-16 19:32 ` [PATCH 0/7] " Ingo Molnar
2009-06-18  2:21   ` Frederic Weisbecker
2009-06-19  3:07   ` Frederic Weisbecker

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=20090619021418.GC7903@nowhere \
    --to=fweisbec@gmail.com \
    --cc=bligh@google.com \
    --cc=fche@redhat.com \
    --cc=jbaron@redhat.com \
    --cc=jiayingz@google.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --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