From: skrishnakar@gmail.com (srikanth krishnakar)
Subject: [ltt-dev] 2.6.29-LTTng-0.116 on RT kernel
Date: Thu, 26 Mar 2009 23:55:06 +0530 [thread overview]
Message-ID: <6213bc560903261125m188ee503xbe0f29328275af5a@mail.gmail.com> (raw)
Message-ID: <20090326182506.LAGmH4jFbJ0RH9Yn_1aMQp0g72XQaOFbe_tFHBlqJuw@z> (raw)
In-Reply-To: <20090326164412.GB5257@Krystal>
On Thu, Mar 26, 2009 at 10:14 PM, Mathieu Desnoyers <
compudj at krystal.dyndns.org> wrote:
> * srikanth krishnakar (skrishnakar at gmail.com) wrote:
> > Hi Mathieu,
> >
> >
> > I had some query regarding implementation of *LTTng* on *RT* kernel. The
> > kernel version used is *Linux-2.6.29*, RT patch version is
> *patch-2.6.29-rt1
> > *and* *LTTng version is *2.6.29-lttng-0.116. *I see few of the LTTng
> commits
> > are already present in RT patch, I see few clashes in
> > include/linux/tracepoint.h file... Do I need to drop certain commits from
> > LTTng-2.6.29-0.116 to cleanly apply and integrate LTTng on top of RT
> kernel
> > ?
> >
>
> It is going to be a case-by-case thing. Some tracepoints commits are
> really needed. The immediate values-related commits can be ignored,
> since they represent an optimisation.
>
> Mathieu
Thanks Mathieu for the response.
I tried resolving few conflicts with but got the compile errors as below:
[root at srikanth linux-2.6.29]# make zImage
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-powerpc
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
CC arch/powerpc/kernel/ptrace.o
In file included from arch/powerpc/kernel/ptrace.c:35:
include/trace/syscall.h:6: error: expected ?)? before ?(? token
include/trace/syscall.h:6: error: expected ?)? before ?(? token
include/trace/syscall.h:6: error: expected ?)? before ?(? token
include/trace/syscall.h:6: warning: function declaration isn?t a prototype
include/trace/syscall.h: In function ?register_trace_syscall_entry?:
include/trace/syscall.h:6: error: ?probe? undeclared (first use in this
function)
include/trace/syscall.h:6: error: (Each undeclared identifier is reported
only once
include/trace/syscall.h:6: error: for each function it appears in.)
include/trace/syscall.h: At top level:
include/trace/syscall.h:6: error: expected ?)? before ?(? token
include/trace/syscall.h:6: warning: function declaration isn?t a prototype
include/trace/syscall.h: In function ?unregister_trace_syscall_entry?:
include/trace/syscall.h:6: error: ?probe? undeclared (first use in this
function)
include/trace/syscall.h: At top level:
include/trace/syscall.h:9: error: expected ?)? before ?(? token
include/trace/syscall.h:9: error: expected ?)? before ?(? token
include/trace/syscall.h:9: error: expected ?)? before ?(? token
include/trace/syscall.h:9: warning: function declaration isn?t a prototype
include/trace/syscall.h: In function ?register_trace_syscall_exit?:
include/trace/syscall.h:9: error: ?probe? undeclared (first use in this
function)
include/trace/syscall.h: At top level:
include/trace/syscall.h:9: error: expected ?)? before ?(? token
include/trace/syscall.h:9: warning: function declaration isn?t a prototype
include/trace/syscall.h: In function ?unregister_trace_syscall_exit?:
include/trace/syscall.h:9: error: ?probe? undeclared (first use in this
function)
arch/powerpc/kernel/ptrace.c: In function ?do_syscall_trace_enter?:
arch/powerpc/kernel/ptrace.c:1028: error: implicit declaration of function
?trace_syscall_entry?
arch/powerpc/kernel/ptrace.c: In function ?do_syscall_trace_leave?:
arch/powerpc/kernel/ptrace.c:1065: error: implicit declaration of function
?trace_syscall_exit?
make[1]: *** [arch/powerpc/kernel/ptrace.o] Error 1
make: *** [arch/powerpc/kernel] Error 2
[root at srikanth linux-2.6.29]#
Which commits from 2.6.29-LTTng-0.116 from can really be dropped and how we
are handling *preempt_enable* of RT before trace ?
Thanks ..
Srikanth
>
>
> > Note : ARCHITECTURE :* PowerPC**-440*
> >
> > Regards
> > Srikanth Krishnakar
> > **********************
>
> > _______________________________________________
> > ltt-dev mailing list
> > ltt-dev at lists.casi.polymtl.ca
> > 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
>
--
"The Good You Do, The Best You GET"
Regards
Srikanth Krishnakar
**********************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.casi.polymtl.ca/pipermail/lttng-dev/attachments/20090326/6381e393/attachment-0003.htm>
next prev parent reply other threads:[~2009-03-26 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 15:59 srikanth krishnakar
2009-03-26 15:59 ` srikanth krishnakar
2009-03-26 15:59 ` srikanth krishnakar
2009-03-26 16:44 ` Mathieu Desnoyers
2009-03-26 18:25 ` srikanth krishnakar [this message]
2009-03-26 18:25 ` srikanth krishnakar
2009-03-26 18:25 ` srikanth krishnakar
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=6213bc560903261125m188ee503xbe0f29328275af5a@mail.gmail.com \
--to=skrishnakar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox