Re: LTTng 0.62 on omap 1611
Mathieu Desnoyers <[email protected]>
| Newsgroups | gmane.linux.kernel.tracing |
|---|---|
| Message-ID | <20070413214445.GB28283@Krystal> |
* Liselene Borges ([email protected]) wrote: > Hi Mathieu, > > I have tried to compile LTTng version 0.6.41, but unfortunately I got this > error message: > > CC arch/arm/kernel/asm-offsets.s > In file included from include/linux/spinlock_types.h:13, > from include/linux/spinlock.h:79, > from include/linux/capability.h:46, > from include/linux/sched.h:45, > from arch/arm/kernel/asm-offsets.c:14: > include/linux/lockdep.h:93: error: array type has incomplete element type > include/linux/lockdep.h:134: error: field 'trace' has incomplete type > make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 > make: *** [prepare0] Error 2 > make: *** Waiting for unfinished jobs.... > HOSTLD scripts/mod/modpost > > So I've tried, disabling Toolkit and Facility Locking and then it shows > problems during linking process, as follows: > > LD init/built-in.o > LD .tmp_vmlinux1 > ltt/built-in.o: In function `ltt_force_switch': > ltt/ltt-relay.c:649: undefined reference to `cmpxchg' > ltt/built-in.o: In function `ltt_ioctl': > ltt/ltt-relay.c:309: undefined reference to `cmpxchg' > ltt/built-in.o: In function `ltt_relay_reserve_slot': > ltt/ltt-relay.c:966: undefined reference to `cmpxchg' > ltt/ltt-relay.c:990: undefined reference to `cmpxchg' > make: *** [.tmp_vmlinux1] Error 1 > Found the issue, it's been fixed in further versions : edit include/asm-generic/atomic.h change : #define atomic_long_cmpxchg(l, old, new) \ ((long)cmpxchg(&((l)->counter), (old), (new))) #define atomic_long_xchg(l, new) (xchg(&((l)->counter), (new))) for #define atomic_long_cmpxchg(l, old, new) \ (atomic_cmpxchg((atomic_t *)(l), (old), (new))) #define atomic_long_xchg(v, new) \ (atomic_xchg((atomic_t *)(l), (new))) It comes from the fact that arm does not define cmpxchg(), but does define atomic_cmpxchg(). > Do you have a suggest where might be the problem? > > Br, > Liselene > > On 4/13/07, Mathieu Desnoyers <[email protected]> wrote: > > > >Hrm, you may want to try a newer LTTng version and see if the problem > >persists. > > > >Mathieu > > > >* Liselene Borges ([email protected]) wrote: > >> Hi Mathieu, > >> > >> I have all my modules set to built-in, so I dont need to load any > >module. > >> Just correcting, I am using Lttng version 0.6.2. > >> > >> Br, > >> Liselene > >> > >> On 4/12/07, Mathieu Desnoyers <[email protected]> wrote: > >> > > >> >* Liselene Borges ([email protected]) wrote: > >> >> Hi all, > >> >> > >> >> I am trying to run LTTng 0.62 in my omap 1611, running linux 2.6.18. > >> >> I have installed ltt-control-0.26. I am testing a simple use case, a > >> >file > >> >> transfer between RAM and MMC card. > >> >> The trace runs fine, but the results are quite wierd. It just apper > >> >these > >> >> instrumentation, as follows: > >> >> > >> >> core.state_dump_facility_load > >> >> core.time_heartbeat > >> >> statedump.enumerate_file_descriptors > >> >> statedump.enumerate_network_ip_interface > >> >> statedump.enumerate_process_state > >> >> statedump.enumerate_vm_maps > >> >> statedump.statedump_end > >> >> > >> >> I have tested it with other versions of lttng (0.5113) and for me it > >> >shows > >> >> more facilities. > >> >> May I am doing something wrong? Is lttng 0.62 arm port ok? > >> >> > >> > > >> >You will need to load the ltt-probe-* kernel modules just before > >> >starting to trace. See the QUICKSTART for details. > >> > > >> >Mathieu > >> > > >> > > >> >> Br, > >> >> Liselene > >> > > >> >> _______________________________________________ > >> >> Ltt-dev mailing list > >> >> [email protected] > >> >> http://listserv.shafik.org/mailman/listinfo/ltt-dev > >> > > >> > > >> >-- > >> >Mathieu Desnoyers > >> >Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal > >> >OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE > >> >9A68 > >> > > > > >-- > >Mathieu Desnoyers > >Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal > >OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE > >9A68 > > -- Mathieu Desnoyers Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68