From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
utrace-devel@redhat.com, Frank Eigler <fche@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] utrace-based ftrace "process" engine, v2
Date: Sat, 21 Mar 2009 08:43:01 +0100 [thread overview]
Message-ID: <20090321074301.GA19384@elte.hu> (raw)
In-Reply-To: <20090321014244.9ADF1FC3AB@magilla.sf.frob.com>
* Roland McGrath <roland@redhat.com> wrote:
> From: Frank Ch. Eigler <fche@redhat.com>
>
> This is v2 of the prototype utrace-ftrace interface. This code is
> based on Roland McGrath's utrace API, which provides programmatic
> hooks to the in-tree tracehook layer. This new patch interfaces
> many of those events to ftrace, as configured by a small number of
> debugfs controls. Here's the
> /debugfs/tracing/process_trace_README:
Please submit changes/enhancements to kernel/trace/* to the tracing
tree maintainers (Steve and me) for review, testing and integration.
Please also post patches against the latest tracing tree:
http://people.redhat.com/mingo/tip.git/README
As this patch does not apply:
Applying patch patches/utrace-based-ftrace-process-engine-v2.patch
patching file include/linux/processtrace.h
patching file kernel/trace/Kconfig
Hunk #1 succeeded at 186 with fuzz 2 (offset 36 lines).
patching file kernel/trace/Makefile
Hunk #1 FAILED at 33.
1 out of 1 hunk FAILED -- rejects in file kernel/trace/Makefile
patching file kernel/trace/trace.h
Hunk #1 succeeded at 7 with fuzz 1.
Hunk #2 FAILED at 31.
Hunk #3 succeeded at 215 with fuzz 2 (offset 43 lines).
Hunk #4 FAILED at 330.
2 out of 4 hunks FAILED -- rejects in file kernel/trace/trace.h
patching file kernel/trace/trace_process.c
Patch patches/utrace-based-ftrace-process-engine-v2.patch does not apply (enforce with -f)
Thanks,
Ingo
next prev parent reply other threads:[~2009-03-21 7:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 1:39 [PATCH 0/3] utrace Roland McGrath
2009-03-21 1:41 ` [PATCH 1/3] signals: tracehook_notify_jctl change Roland McGrath
2009-03-21 1:41 ` [PATCH 2/3] utrace core Roland McGrath
2009-03-21 8:49 ` Andrew Morton
2009-03-21 14:08 ` Renzo Davoli
2009-03-21 14:34 ` Ingo Molnar
2009-03-21 16:37 ` Renzo Davoli
2009-03-21 16:44 ` Ingo Molnar
2009-03-23 4:34 ` Roland McGrath
2009-03-23 4:35 ` Roland McGrath
2009-03-23 10:57 ` Will Newton
2009-03-21 1:42 ` [PATCH 3/3] utrace-based ftrace "process" engine, v2 Roland McGrath
2009-03-21 7:43 ` Ingo Molnar [this message]
2009-03-21 8:39 ` Andrew Morton
2009-03-21 9:12 ` Ingo Molnar
2009-03-21 11:19 ` Andrew Morton
2009-03-21 11:51 ` Frank Ch. Eigler
2009-03-21 12:04 ` Andrew Morton
2009-03-21 12:57 ` Frank Ch. Eigler
2009-03-21 15:45 ` Ingo Molnar
2009-03-21 20:35 ` Diego Calleja
2009-03-22 12:17 ` Ingo Molnar
2009-03-21 21:34 ` Andrew Morton
2009-03-21 21:51 ` Frank Ch. Eigler
2009-03-21 22:02 ` Linus Torvalds
2009-03-21 22:20 ` Frank Ch. Eigler
2009-03-21 22:37 ` Alexey Dobriyan
2009-03-21 23:38 ` Frank Ch. Eigler
2009-03-22 10:25 ` Ingo Molnar
2009-03-23 5:33 ` Roland McGrath
2009-03-23 5:20 ` Roland McGrath
2009-03-22 12:37 ` Ingo Molnar
2009-03-23 13:48 ` Alexey Dobriyan
2009-03-23 15:14 ` Oleg Nesterov
2009-03-23 21:44 ` Theodore Tso
2009-03-30 22:18 ` Andrew Morton
2009-03-30 22:52 ` Frank Ch. Eigler
2009-03-31 9:17 ` Peter Zijlstra
2009-03-31 11:27 ` Peter Zijlstra
2009-03-31 11:38 ` Frank Ch. Eigler
2009-03-31 16:25 ` Christoph Hellwig
2009-03-31 20:54 ` Roland McGrath
2009-03-21 21:48 ` Frank Ch. Eigler
2009-03-22 12:08 ` Ingo Molnar
2009-03-22 12:53 ` Ingo Molnar
2009-03-23 20:25 ` Frank Ch. Eigler
2009-03-23 20:39 ` Linus Torvalds
2009-03-23 5:09 ` Roland McGrath
2009-03-24 5:29 ` Ananth N Mavinakayanahalli
2009-03-24 5:54 ` Andrew Morton
2009-03-24 6:10 ` Ananth N Mavinakayanahalli
2009-03-23 4:49 ` Roland McGrath
2009-03-23 6:34 ` 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=20090321074301.GA19384@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fche@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=rostedt@goodmis.org \
--cc=utrace-devel@redhat.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.