From: Peter Zijlstra <peterz@infradead.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@kernel.org>,
Taeung Song <treeze.taeung@gmail.com>,
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: Sat, 27 Feb 2016 16:13:57 +0100 [thread overview]
Message-ID: <20160227151357.GE6356@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160226135713.GU8720@kernel.org>
On Fri, Feb 26, 2016 at 10:57:13AM -0300, Arnaldo Carvalho de Melo wrote:
> Ingo, Peter, have you guys followed this case?
>
> Summary: Some tracepoint have multiple fields with the same name, 'nr',
> the first one is a unique syscall ID, the other is a syscall
> argument:
I'm all for pushing the limits on tracepoint ABI. I'm all for making it
less rigid. So if we can get away with changing this under the promise
of helping fixup fallout, I'm all for it.
That means we can always just change tracepoints, and they're not really
ABI at all.
next prev parent reply other threads:[~2016-02-27 15:14 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
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 ` Peter Zijlstra [this message]
2016-02-29 14:21 ` [RFC] Re: [PATCH v3 1/2] tracing/syscalls: Rename variable 'nr' to '__syscall_nr' 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=20160227151357.GE6356@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=treeze.taeung@gmail.com \
/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