From: ebiederm@xmission.com (Eric W. Biederman)
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
containers@lists.osdl.org, fweisbec@gmail.com,
LKML <linux-kernel@vger.kernel.org>,
srostedt@redhat.com,
Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
"Serge E. Hallyn" <serue@us.ibm.com>
Subject: Re: [PATCH 1/3] ftrace: add function tracing to single thread
Date: Tue, 25 Nov 2008 23:02:10 -0800 [thread overview]
Message-ID: <m1zljn7yx9.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20081126063201.GF9732@elte.hu> (Ingo Molnar's message of "Wed, 26 Nov 2008 07:32:01 +0100")
Ingo Molnar <mingo@elte.hu> writes:
> i dont see the point of the complexity you are advocating. 99.9% of
> the users run a unique PID space.
I'm not advocating complexity. I'm advocating using the same APIs as
the rest of the kernel, for doing the same functions.
> Tracing is about keeping stuff simple. On containers we could also
> trace the namespace ID (is there an easy ID for the namespace, as an
> easy extension to the very nice PID concept that Unix introduced
> decades ago?) and be done with it.
I don't really care about the pid namespace in this context.
I am just asking that we compare a different field in the task struct.
I am asking that we don't accumulate new users of an old crufty bug prone
API, for no good reason.
I'm asking that we don't be different for no good reason.
Eric
next prev parent reply other threads:[~2008-11-26 7:02 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 22:34 [PATCH 0/3] ftrace: new features Steven Rostedt
2008-11-25 22:34 ` [PATCH 1/3] ftrace: add function tracing to single thread Steven Rostedt
2008-11-25 22:42 ` Andrew Morton
2008-11-25 23:01 ` Steven Rostedt
2008-11-25 23:31 ` Andrew Morton
2008-11-26 0:11 ` Steven Rostedt
2008-11-26 0:53 ` Dave Hansen
2008-11-26 1:01 ` Steven Rostedt
2008-11-26 4:50 ` Eric W. Biederman
2008-11-26 5:01 ` Steven Rostedt
2008-11-26 6:23 ` Eric W. Biederman
2008-11-26 6:32 ` Ingo Molnar
2008-11-26 7:02 ` Eric W. Biederman [this message]
2008-11-26 7:18 ` Ingo Molnar
2008-11-26 8:48 ` Eric W. Biederman
2008-11-26 5:20 ` Eric W. Biederman
2008-11-26 16:36 ` Steven Rostedt
2008-11-26 0:02 ` Frédéric Weisbecker
2008-11-26 0:16 ` Steven Rostedt
2008-11-25 22:34 ` [PATCH 2/3] ftrace: use code patching for ftrace return tracer Steven Rostedt
2008-11-26 0:13 ` Frédéric Weisbecker
2008-11-26 0:23 ` Steven Rostedt
2008-11-25 22:34 ` [PATCH 3/3] ftrace: let function tracing and function return run together Steven Rostedt
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=m1zljn7yx9.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.osdl.org \
--cc=dave@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=serue@us.ibm.com \
--cc=srostedt@redhat.com \
--cc=sukadev@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.