From: Taeung Song <treeze.taeung@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Lai Jiangshan <jiangshanlai@gmail.com>
Subject: Re: [RFC] Re: [PATCH v3 1/2] tracing/syscalls: Rename variable 'nr' to '__syscall_nr'
Date: Sun, 28 Feb 2016 16:43:50 +0900 [thread overview]
Message-ID: <56D2A536.9090503@gmail.com> (raw)
In-Reply-To: <20160227133431.0713749f@grimm.local.home>
On 02/28/2016 03:34 AM, Steven Rostedt wrote:
> On Sun, 28 Feb 2016 01:10:19 +0900
> Taeung Song <treeze.taeung@gmail.com> wrote:
>
>> I got it :-)
>> In conclusion, output of format
>> (/sys/kernel/debug/tracing/events/syscalls/*/format)
>> has __syscall_nr for syscall number but the kernel structure
>> 'syscall_trace_enter' and 'syscall_trace_exit' have not __syscall_nr
>> variable.
>> Is it right ?
>
> Correct. Just change the output of the format file. Not the data
> structures in the kernel.
>
> Thanks,
>
> -- Steve
Thank you !! :-)
Taeung
next prev parent reply other threads:[~2016-02-28 7:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:14 Taeung Song
2016-02-26 13:57 ` [RFC] " Arnaldo Carvalho de Melo
2016-02-26 18:23 ` Steven Rostedt
2016-02-26 19:03 ` Arnaldo Carvalho de Melo
2016-02-27 16:10 ` Taeung Song
2016-02-27 18:34 ` Steven Rostedt
2016-02-28 7:43 ` Taeung Song [this message]
2016-03-05 8:13 ` [tip:perf/core] tracing/syscalls: Rename "/format" tracepoint field name "nr" to "__syscall_nr: tip-bot for Taeung Song
2016-02-27 15:13 ` [RFC] Re: [PATCH v3 1/2] tracing/syscalls: Rename variable 'nr' to '__syscall_nr' Peter Zijlstra
2016-02-29 14:21 ` Arnaldo Carvalho de Melo
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=56D2A536.9090503@gmail.com \
--to=treeze.taeung@gmail.com \
--cc=acme@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome