From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] latency tracer
Date: Sat, 9 Feb 2008 08:37:56 +0100 [thread overview]
Message-ID: <20080209073756.GA13141@elte.hu> (raw)
In-Reply-To: <20080208232306.6e8a8162.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 8 Feb 2008 22:45:22 +0100 Ingo Molnar <mingo@elte.hu> wrote:
>
> > Linus, please pull the latency tracer tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git
> >
> > Find the shortlog below.
> >
> > This is the latency tracer from -rt
>
> I've never seen any of this code before and googling several of the
> patch titles turns up this email and nothing else.
there might be some confusion here. Google for "mcount tracing utility"
- there's 2270 hits. There's been 8 full series posted to lkml in the
past month:
Date: Thu, 03 Jan 2008 02:16:09 -0500
Subject: [RFC PATCH 00/11] mcount tracing utility
Date: Wed, 09 Jan 2008 18:29:14 -0500
Subject: [RFC PATCH 00/22 -v2] mcount and latency tracing utility -v2
Date: Tue, 15 Jan 2008 15:49:07 -0500
Subject: [RFC PATCH 00/30 v3] mcount and latency tracing utility -v3
Date: Mon, 21 Jan 2008 10:22:31 -0500
Subject: [RFC PATCH 00/23 -v4] mcount and latency tracing utility -v4
Date: Wed, 23 Jan 2008 11:02:36 -0500
Subject: [PATCH 00/20 -v5] mcount and latency tracing utility -v5
Date: Fri, 25 Jan 2008 23:21:52 -0500
Subject: [PATCH 00/23 -v6] mcount and latency tracing utility -v6
Date: Tue, 29 Jan 2008 22:15:21 -0500
Subject: [PATCH 00/22 -v7] mcount and latency tracing utility -v7
Date: Wed, 30 Jan 2008 16:03:57 -0500
Subject: [PATCH 00/23 -v8] mcount and latency tracing utility -v8
it derives from the same latency tracer code that we wrote for -rt that
has been around for years:
http://people.redhat.com/mingo/latency-tracing-patches/
we renamed the concept to 'ftrace' during pre-merge cleanups, perhaps
that is what caused you to not recognize this? (mcount is a confusing
name and ties it to a gcc feature while there's nothing gcc specific
about this concept.)
Ingo
next prev parent reply other threads:[~2008-02-09 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 21:45 [git pull] latency tracer Ingo Molnar
2008-02-09 7:01 ` Ingo Molnar
2008-02-09 7:23 ` Andrew Morton
2008-02-09 7:37 ` Ingo Molnar [this message]
2008-02-09 8:05 ` Andrew Morton
2008-02-09 14:21 ` Ingo Molnar
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=20080209073756.GA13141@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linux-foundation.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 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.