From: Tom Zanussi <tzanussi@gmail.com>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, rostedt@goodmis.org,
lizf@cn.fujitsu.com
Subject: Re: [PATCH 3/3] tracing/syscalls: Use long for syscall ret format and field definitions
Date: Tue, 06 Oct 2009 22:59:22 -0500 [thread overview]
Message-ID: <1254887962.28917.101.camel@tropicana> (raw)
In-Reply-To: <c62985530910060015t74d8c116i8593839e6d8a3af5@mail.gmail.com>
On Tue, 2009-10-06 at 09:15 +0200, Frédéric Weisbecker wrote:
> 2009/10/6, Tom Zanussi <tzanussi@gmail.com>:
> > The syscall event definitions use long for the syscall exit ret value,
> > but unsigned long for the same thing in the format and field
> > definitions. Change them all to long.
>
>
> Thanks.
>
> We may perhaps also want to change struct syscall_trace_exit
> according to that?
> That won't change the code behaviour, just the logic while
> reviewing.
>
> It's just a neat, this patch itself is fine.
>
Yeah, that should have been part of it too. I'll submit another patch
later doing that.
Tom
>
> >
> > Signed-off-by: Tom Zanussi <tzanussi@gmail.com>
> > ---
> > kernel/trace/trace_syscalls.c | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/trace/trace_syscalls.c b/kernel/trace/trace_syscalls.c
> > index 9fbce6c..527e17e 100644
> > --- a/kernel/trace/trace_syscalls.c
> > +++ b/kernel/trace/trace_syscalls.c
> > @@ -166,7 +166,7 @@ int syscall_exit_format(struct ftrace_event_call *call,
> > struct trace_seq *s)
> > "\tfield:%s %s;\toffset:%zu;\tsize:%zu;\n"
> > "\tfield:%s %s;\toffset:%zu;\tsize:%zu;\n",
> > SYSCALL_FIELD(int, nr),
> > - SYSCALL_FIELD(unsigned long, ret));
> > + SYSCALL_FIELD(long, ret));
> > if (!ret)
> > return 0;
> >
> > @@ -212,7 +212,7 @@ int syscall_exit_define_fields(struct ftrace_event_call
> > *call)
> > if (ret)
> > return ret;
> >
> > - ret = trace_define_field(call, SYSCALL_FIELD(unsigned long, ret), 0,
> > + ret = trace_define_field(call, SYSCALL_FIELD(long, ret), 0,
> > FILTER_OTHER);
> >
> > return ret;
> > --
> > 1.6.4.GIT
> >
> >
next prev parent reply other threads:[~2009-10-07 4:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 6:00 [PATCH 0/3] a few tracing bugfixes Tom Zanussi
2009-10-06 6:00 ` [PATCH 1/3] perf trace: Remove unused code in builtin-trace.c Tom Zanussi
2009-10-06 12:16 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 6:00 ` [PATCH 2/3] perf trace: Update eval_flag() flags array to match interrupt.h Tom Zanussi
2009-10-06 12:16 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 13:27 ` [PATCH 2/3] " Christoph Hellwig
2009-10-06 15:19 ` Frederic Weisbecker
2009-10-06 15:21 ` Christoph Hellwig
2009-10-06 15:22 ` Frederic Weisbecker
2009-10-06 15:24 ` Christoph Hellwig
2009-10-06 21:42 ` Frederic Weisbecker
2009-10-07 1:17 ` Steven Rostedt
2009-10-06 15:25 ` Frederic Weisbecker
2009-10-11 8:53 ` Ingo Molnar
2009-10-11 12:21 ` Christoph Hellwig
2009-10-16 8:47 ` Ingo Molnar
2009-10-06 6:00 ` [PATCH 3/3] tracing/syscalls: Use long for syscall ret format and field definitions Tom Zanussi
2009-10-06 7:15 ` Frédéric Weisbecker
2009-10-07 3:59 ` Tom Zanussi [this message]
2009-10-06 12:17 ` [tip:perf/urgent] " tip-bot for Tom Zanussi
2009-10-06 7:16 ` [PATCH 0/3] a few tracing bugfixes Frédéric 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=1254887962.28917.101.camel@tropicana \
--to=tzanussi@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--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®