Re: [ltt-dev] LTTng 0.74 for Linux 2.6.28 (ext4 tracepoints)(fixed in LTTng 0.78)

[Mathieu Desnoyers]

* Mathieu Desnoyers (compudj@xxxxxxxxxxxxxxxxxx) wrote:
> * Theodore Tso (tytso@xxxxxxx) 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.
>

Actually, the x86_32 2.6.28 build was broken because of a bad patch
hunk which caused this problem. I fixed it in lttng 0.81. The port to
2.6.29-rc1 should some in a few days.

Thanks for the report,

Mathieu

> Mathieu
> 
> > 						- Ted
> > 
> 
> -- 
> Mathieu Desnoyers
> OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev@xxxxxxxxxxxxxxxxxxxxx
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev

-- 
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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/