From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
mathieu.desnoyers@polymtl.ca,
Steven Rostedt <rostedt@goodmis.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
Subject: Re: [PATCH 3/4] tracing: pass proto and args to DEFINE_TRACE
Date: Fri, 17 Apr 2009 14:53:38 +0200 [thread overview]
Message-ID: <20090417125338.GA24283@elte.hu> (raw)
In-Reply-To: <20090417070513.GA24860@infradead.org>
* Christoph Hellwig <hch@infradead.org> wrote:
> Then again I'd really wish we could get Steve's recents bits
> merged for various reasons. [...]
I symphathise with your desire to have the latest and greatest stuff
upstream right now (i get asked this all the time - _everyone_ wants
their important stuff upstream, yesterday (and everyone else's
unstable unnecessary crap should wait)), but there's no way we'll
rush these new tracing features upstream now. They are not yet
complete and there's a set of new users whose needs have to be
observed and designed in.
That is how the upstream development cycle works: stuff added after
the merge window goes upstream in the next merge window, at the
earliest. (I.e. in about 2 months from now.)
> [...] The whole DEFINE_TRACE thing only appeared in 2.6.30 and
> releasing that one kernel with the half-baked inferior version
> sounds like a really bad idea.
The current upstream code in .30 is fully functional and useful to
all the subsystems that are making use of it - so your attack on it
is a bit puzzling to me.
You showed up when, some two weeks ago or so, in the merge window?
That's generally pretty much the worst time to ask for more
features. The moral of the story is really: if you feel strongly
about features in an area, get involved sooner.
Module support (which your complaint really boils down to) was never
really popular with users of this stuff: the pre-.30 facilities were
exported to modules all along, but were rarely used from that angle
(for understandable reasons). Most tracing code contributions and
enhancements came from the direction of non-modular core kernel
facilities.
Linus doesnt even _use_ modular kernels - neither do i ;)
Yes, once a facility proves to be successful (this is about the
fifth version - it all evolved gradually along several kernel
releases), everyone jumps on it and wants new features, preferably
yesterday.
Thanks,
Ingo
next prev parent reply other threads:[~2009-04-17 12:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 6:35 [PATCH] tracing WIP patches Jeremy Fitzhardinge
2009-04-17 6:35 ` [PATCH 1/4] tracing: move __DO_TRACE out of line Jeremy Fitzhardinge
2009-04-17 15:46 ` Ingo Molnar
2009-04-17 16:10 ` Mathieu Desnoyers
2009-04-17 16:23 ` Ingo Molnar
2009-04-17 16:47 ` Jeremy Fitzhardinge
2009-04-17 19:31 ` Jeremy Fitzhardinge
2009-04-17 19:46 ` Ingo Molnar
2009-04-17 19:57 ` Steven Rostedt
2009-04-17 19:58 ` Jeremy Fitzhardinge
2009-04-17 20:06 ` Steven Rostedt
2009-04-18 6:53 ` Mathieu Desnoyers
2009-04-18 14:16 ` Steven Rostedt
2009-04-19 3:59 ` Mathieu Desnoyers
2009-04-19 23:38 ` Jeremy Fitzhardinge
2009-04-20 21:39 ` Mathieu Desnoyers
2009-04-19 23:40 ` Jeremy Fitzhardinge
2009-04-20 21:47 ` Mathieu Desnoyers
2009-04-17 6:35 ` [PATCH 2/4] x86/pvops: target CREATE_TRACE_POINTS to particular subsystems Jeremy Fitzhardinge
2009-04-17 15:55 ` Steven Rostedt
2009-04-17 16:14 ` Jeremy Fitzhardinge
2009-04-17 16:32 ` Steven Rostedt
2009-04-17 16:48 ` Jeremy Fitzhardinge
2009-04-17 16:57 ` Steven Rostedt
2009-04-17 17:14 ` Jeremy Fitzhardinge
2009-04-17 17:33 ` Steven Rostedt
2009-04-17 18:11 ` Jeremy Fitzhardinge
2009-04-17 6:35 ` [PATCH 3/4] tracing: pass proto and args to DEFINE_TRACE Jeremy Fitzhardinge
2009-04-17 6:48 ` Christoph Hellwig
2009-04-17 6:58 ` Jeremy Fitzhardinge
2009-04-17 7:05 ` Christoph Hellwig
2009-04-17 12:53 ` Ingo Molnar [this message]
2009-04-17 15:21 ` Mathieu Desnoyers
2009-04-17 6:35 ` [PATCH 4/4] tracing: avoid warnings from zero-arg tracepoints Jeremy Fitzhardinge
2009-04-17 15:53 ` Steven Rostedt
2009-04-17 15:53 ` Ingo Molnar
2009-04-17 16:10 ` [tip:tracing/core] " tip-bot for Jeremy Fitzhardinge
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=20090417125338.GA24283@elte.hu \
--to=mingo@elte.hu \
--cc=hch@infradead.org \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--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