Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints)	(fixed in LTTng 0.78)
Date: Wed, 14 Jan 2009 20:45:21 -0500	[thread overview]
Message-ID: <20090115014521.GG7458@Krystal> (raw)
In-Reply-To: <20090114001346.GB14730@mit.edu>

* Theodore Tso (tytso at mit.edu) wrote:
> On Tue, Jan 13, 2009 at 05:58:27PM -0500, Mathieu Desnoyers wrote:
> > > 
> > > -ECANTBUILD
> > > 
> > Thanks for the report. This should be fixed in LTTng 0.78 now.
> 
> Out of curiosity, do you maintain a branch of LTTNG versus any of the
> -rc kernels, or do you only track the stable kernels?  I tried pulling
> LTTNG 0.78 against the most recent Linus mainline and got a whole pile
> of conflicts.
> 
> I then tried building LTTng 0.78 and got build failures:
> 
>   CC      arch/x86/kernel/init_task.o
> distcc[27501] ERROR: compile /var/cache/ccache/init_task.tmp.closure.27497.i on localhost failed
> /usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: unknown field ?user_markers_mutex? specified in initializer
> /usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: warning: braces around scalar initializer
> /usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: warning: (near initialization for ?init_task.latency_record_count?)
> /usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: field name not in record or union initializer
> /usr/projects/linux/ext4/arch/x86/kernel/init_task.c:35: error: (near initialization for ?init_task.latency_record_count?)
> 
> Looks like CONFIG_MARKERS_USERSPAC is busted....
> 

Hi Ted,

I'm currently integrating Lai's work to the 2.6.28 lttng branch (ascii
output !) :) and the next step will be to move to 2.6.29-rc1. I'll keep
you posted. Note that you can just leave the 

#New revamped userspace markers

markers-userspace.patch
markers-userspace-x86.patch
markers-userspace-x86_64.patch
sparc64-support-userspace-tracing.patch

Out of the patchset and it should not hurt the kernel tracing part at
all.?Note that these 4 patches are planned to be heavily reworked before
lkml submission.

Mathieu

> 						- Ted
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68



  reply	other threads:[~2009-01-15  1:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-09 23:54 [ltt-dev] LTTng 0.73 for Linux 2.6.28 Mathieu Desnoyers
2009-01-10 16:11 ` [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints) Mathieu Desnoyers
2009-01-13 22:33   ` KOSAKI Motohiro
2009-01-13 22:58     ` [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints) (fixed in LTTng 0.78) Mathieu Desnoyers
2009-01-13 23:57       ` KOSAKI Motohiro
2009-01-14  5:20         ` Mathieu Desnoyers
2009-01-14  0:13       ` Theodore Tso
2009-01-15  1:45         ` Mathieu Desnoyers [this message]
2009-01-15  3:20           ` Mathieu Desnoyers
2009-01-12 10:33 ` [ltt-dev] LTTng 0.73 for Linux 2.6.28 Akyurek, Ali (EXT)
2009-01-12 16:38   ` Mathieu Desnoyers

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=20090115014521.GG7458@Krystal \
    --to=compudj@krystal.dyndns.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