linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
	cl@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [RFC PATCH 1/4] kmemtrace: Core implementation.
Date: Fri, 18 Jul 2008 15:07:20 -0500	[thread overview]
Message-ID: <1216411640.3712.16.camel@calx> (raw)
In-Reply-To: <20080718194059.GA5238@localhost>

On Fri, 2008-07-18 at 22:40 +0300, Eduard - Gabriel Munteanu wrote:
> On Fri, Jul 18, 2008 at 05:38:04PM +0300, Pekka Enberg wrote:
> > Hi Eduard-Gabriel,
> > > I do expect to keep things source-compatible, but even
> > > binary-compatible? Developers debug and write patches on the latest kernel,
> > > not on a 6-month-old kernel. Isn't it reasonable that they would
> > > recompile kmemtrace along with the kernel?
> > 
> > Yes, I do think it's unreasonable. I, for one, am hoping distributions
> > will pick up the kmemtrace userspace at some point after which I don't
> > need to ever compile it myself.
> 
> Ok, I agree it's nice to have it in distros. I wasn't planning for this,
> but it's good to know others' expectations.

It's worth pointing out that this is one of the big downfalls of things
like systemtap. If a tool can't just work out of the box for a distro,
it's basically a non-starter for most users.

-- 
Mathematics is the supreme nostalgia of our time.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-07-18 20:07 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  0:46 [RFC PATCH 0/4] kmemtrace RFC (resubmit 1) Eduard - Gabriel Munteanu
2008-07-17  0:46 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-17  0:46   ` [RFC PATCH 2/4] kmemtrace: SLAB hooks Eduard - Gabriel Munteanu
2008-07-17  0:46     ` [RFC PATCH 3/4] kmemtrace: SLUB hooks Eduard - Gabriel Munteanu
2008-07-17  0:46       ` [RFC PATCH 4/4] kmemtrace: SLOB hooks Eduard - Gabriel Munteanu
2008-07-17  7:43         ` Pekka Enberg
2008-07-17 15:46           ` Matt Mackall
2008-07-17  7:46       ` [RFC PATCH 3/4] kmemtrace: SLUB hooks Pekka Enberg
2008-07-17 18:06         ` Eduard - Gabriel Munteanu
2008-07-17  7:38     ` [RFC PATCH 2/4] kmemtrace: SLAB hooks Pekka Enberg
2008-07-17  8:01   ` [RFC PATCH 1/4] kmemtrace: Core implementation Pekka Enberg
2008-07-17 18:32     ` Eduard - Gabriel Munteanu
2008-07-18  8:48       ` Pekka J Enberg
2008-07-18 10:13         ` Eduard - Gabriel Munteanu
2008-07-18 14:38           ` Pekka Enberg
2008-07-18 19:40             ` Eduard - Gabriel Munteanu
2008-07-18 20:07               ` Matt Mackall [this message]
2008-07-17 21:34   ` Randy Dunlap
2008-07-17 23:49     ` Eduard - Gabriel Munteanu
2008-07-22 18:31 [RFC PATCH 0/4] kmemtrace RFC (resend 2) Eduard - Gabriel Munteanu
2008-07-22 18:31 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-22 21:28   ` Frank Ch. Eigler
2008-07-23  0:50     ` Eduard - Gabriel Munteanu
2008-07-23  0:55       ` Eduard - Gabriel Munteanu
2008-07-23  1:26       ` Frank Ch. Eigler
2008-07-22 18:36 [RFC PATCH 0/4] kmemtrace RFC (resend 2, fixed wrong Cc) Eduard - Gabriel Munteanu
2008-07-22 18:36 ` [RFC PATCH 1/4] kmemtrace: Core implementation Eduard - Gabriel Munteanu
2008-07-28  9:24   ` Pekka Enberg
2008-07-28 16:29     ` Mathieu Desnoyers
2008-07-28 17:09       ` Matt Mackall
2008-07-28 17:35       ` Eduard - Gabriel Munteanu
2008-07-29  8:25         ` Pekka Enberg

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=1216411640.3712.16.camel@calx \
    --to=mpm@selenic.com \
    --cc=cl@linux-foundation.org \
    --cc=eduard.munteanu@linux360.ro \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=rdunlap@xenotime.net \
    /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