linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org,
	"Theodore Ts'o" <tytso@mit.edu>,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: LTTng 0.89 for Linux 2.6.29-rc3
Date: Thu, 5 Feb 2009 07:18:41 -0800	[thread overview]
Message-ID: <20090205151841.GF6915@linux.vnet.ibm.com> (raw)
In-Reply-To: <20090205150242.GA27895@Krystal>

On Thu, Feb 05, 2009 at 10:02:42AM -0500, Mathieu Desnoyers wrote:
> * Paul E. McKenney (paulmck@linux.vnet.ibm.com) wrote:
> > On Fri, Jan 30, 2009 at 03:07:57PM -0500, Mathieu Desnoyers wrote:
> > > Hi,
> > > 
> > > I just ported LTTng to the 2.6.29-rc3 kernel. It includes the following
> > > changes :
> > > 
> > > - Tree RCU instrumentation
> > > - Updated ext4 and jbd2 instrumentation
> > > 
> > > Please feel free to try it and report any success/problem you may have.
> > > Note that cross-build has been slightly less tested this time because
> > > I'll have to upgrade many of my compilers to a version compatible with
> > > kernel 2.6.29-rc.
> > > 
> > > It also includes the recently added kprobes support through a simple
> > > 
> > > echo symbol_name > /mnt/debugfs/ltt/kprobes/enable
> > > 
> > > It's available at the new LTTng website :
> > > 
> > > http://www.lttng.org/
> > 
> > Hello, Matheiu,
> > 
> > When I try to apply this to v2.6.29-rc3, I get the following:
> > 
> > 	can't find file to patch at input line 61
> > 	Perhaps you used the wrong -p or --strip option?
> > 	The text leading up to this was:
> > 	--------------------------
> > 	|get_ltt_root() is necessary for ltt-trace-control to create subdirs in
> > 	ltt's
> > 	|debugfs dir.
> > 	|
> > 	|From: Zhao Lei <zhaolei@cn.fujitsu.com>
> > 	|Signed-off-by: Zhao Lei <zhaolei@cn.fujitsu.com>
> > 	|Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
> > 	|---
> > 	| include/linux/ltt-core.h |    8 ++++++++
> > 	| ltt/ltt-core.c           |   14 ++++++++++++++
> > 	| ltt/ltt-relay.c          |    8 +-------
> > 	| 3 files changed, 23 insertions(+), 7 deletions(-)
> > 	|
> > 	|Index: linux-2.6-lttng/include/linux/ltt-core.h
> > 	|===================================================================
> > 	|--- linux-2.6-lttng.orig/include/linux/ltt-core.h      2009-01-15
> > 	15:55:18.000000000 -0500
> > 	|+++ linux-2.6-lttng/include/linux/ltt-core.h   2009-01-15
> > 	15:55:24.000000000 -0500
> > 
> > Help?
> > 
> 
> Hi Paul,
> 
> I must admit I'm a bit puzzled. I've tried to quilt push -a both 
> LTTng 0.89 and LTTng 0.92 taken from the website and they both apply
> correctly on 2.6.29-rc3. When I quilt pop -a, neither of those 3 files
> (include/linux/ltt-core.h, ltt/ltt-core.c, ltt/ltt-relay.c) are stucked
> in my tree.
> 
> I've used files from :
> 
> http://www.lttng.org/files/lttng/patch-2.6.29-rc3-lttng-0.92.tar.bz2
> 
> Which tarballs are you using exactly ?

That is indeed the one that I am using.

> I guess you need to apply them to your existing tree, so pointing you to
> git.kernel.org lttng tree won't help much here.

I am attempting to apply to v2.6.29-rc3, which is commit
18e352e4a73465349711a9324767e1b2453383e2 in the linux-2.6 git tree.

Later on, I might well want to apply on top of some other stuff, but
figured I should try it straight first.  ;-)

							Thanx, Paul

> Mathieu
> 
> > 							Thanx, Paul
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

  reply	other threads:[~2009-02-05 15:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 20:07 LTTng 0.89 for Linux 2.6.29-rc3 Mathieu Desnoyers
2009-02-05 14:04 ` Paul E. McKenney
2009-02-05 15:02   ` Mathieu Desnoyers
2009-02-05 15:18     ` Paul E. McKenney [this message]
2009-02-05 15:38       ` [ltt-dev] " Mathieu Desnoyers
2009-02-05 15:58         ` Paul E. McKenney
2009-02-05 16:22           ` Trilok Soni
2009-02-05 18:01             ` Paul E. McKenney
2009-02-05 18:31               ` Mathieu Desnoyers
2009-02-05 18:44                 ` Paul E. McKenney
2009-02-05 20:22                   ` Mathieu Desnoyers
2009-02-05 21:04                     ` Paul E. McKenney
2009-02-05 21:06                       ` Mathieu Desnoyers
2009-02-06  0:33                         ` Paul E. McKenney
2009-02-06  2:00                           ` Mathieu Desnoyers
2009-02-06 13:48                             ` Paul E. McKenney
2009-02-06 20:03                               ` Mathieu Desnoyers
2009-02-06 21:37                                 ` Paul E. McKenney
2009-02-08 15:47                                   ` Paul E. McKenney
2009-02-05 16:28           ` Trilok Soni

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=20090205151841.GF6915@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).