[linux-yocto] 3.10 and lttng-modules

[Bruce Ashfield]

On 13-08-26 7:46 PM, Tom Zanussi wrote:
> On Mon, 2013-08-26 at 19:40 -0400, Bruce Ashfield wrote:
>> On Mon, Aug 26, 2013 at 7:36 PM, Bruce Ashfield
>> <bruce.ashfield at windriver.com> wrote:
>>> On 13-08-26 7:33 PM, Darren Hart wrote:
>>>>
>>>> Hi Bruce,
>>>>
>>>> The world build for genericx86 tripped over a compilation failure for
>>>> lttng-modules:
>>>>
>>>> ...
>>>> |   CC
>>>> [M]
>>>> /build/yocto/master/genericx86_20130826112225/build/tmp/work/genericx86-poky-linux/lttng-modules/2.2.0+gitAUTOINC+1b26381c19-r0/git/probes/lttng-probe-printk.o
>>>> | In file included
>>>> from
>>>> /build/yocto/master/genericx86_20130826112225/build/tmp/work/genericx86-poky-linux/lttng-modules/2.2.0+gitAUTOINC+1b26381c19-r0/git/probes/../instrumentation/events/lttng-module/../../../probes/define_trace.h:148:0,
>>>> |
>>>> from
>>>> /build/yocto/master/genericx86_20130826112225/build/tmp/work/genericx86-poky-linux/lttng-modules/2.2.0+gitAUTOINC+1b26381c19-r0/git/probes/../instrumentation/events/lttng-module/printk.h:64,
>>>> |
>>>> from
>>>> /build/yocto/master/genericx86_20130826112225/build/tmp/work/genericx86-poky-linux/lttng-modules/2.2.0+gitAUTOINC+1b26381c19-r0/git/probes/lttng-probe-printk.c:39:
>>>> |
>>>> /build/yocto/master/genericx86_20130826112225/build/tmp/work/genericx86-poky-linux/lttng-modules/2.2.0+gitAUTOINC+1b26381c19-r0/git/probes/../instrumentation/events/lttng-module/../../../probes/lttng-events.h:151:6:
>>>> error: conflicting types for 'trace_console'
>>>> |  void trace_##_name(_proto);
>>>> ...
>>>>
>>>> There are several others. Quickly reproducible with:
>>>>
>>>> $ bitbake lttng-modules
>>>>
>>>> Is this a known issue with the 3.10 kernel?
>>>
>>>
>>> Known at the moment ... no, since my builds didn't trigger lttng modules
>>> to be built. And actually, it's one of the reasons I prefer all modules
>>> to be in-tree versus out of tree :)
>>>
>>> But it's also not something hard to fix. When LTSI content becomes available
>>> we'll have an in tree version again, but in the mean time
>>> we can just patch lttng modules, via an uprev or bug fix.
>>>
>>> I wouldn't hold the merge on this (we can't hold it on everything), so
>>> my suggestion is to open a bug and we can have a look tomorrow.
>>
>> Looks like 2.2.1 fixes it:
>>
>> 2013-07-11 LTTng modules 2.2.1:
>>
>> * Fix: double length of __dynamic_len array
>> * Fix printk instrumentation
>> * Introduce __dynamic_array_enc_ext_2() and tp_memcpy_dyn_2()
>> * Fix: ring buffer: get_subbuf() checks should be performed on "consumed"
>> * Fix: SWITCH_FLUSH new sub-buffer checks
>> * Fix: ring buffer: handle concurrent update in nested buffer wrap around
>> * Fix: handle writes of length 0
>> * Fix: ring buffer: RING_BUFFER_FLUSH ioctl buffer corruption
>>
>> I can poke at it more later, as well, but maybe TomZ has cycles to update it ?
>>
>
> Well, it's not like I have extra cycles, but I'll look into it.

:P

>
> What branch is this, mut?

You should be able to see it just using master and building lttng-modules,
just make sure you've set the preferred kernel version to 3.10
(if my other patches that make it the default haven't merged).

Bruce

>
> Tom
>
>> Bruce
>>
>>>
>>> Bruce
>>>
>>>
>>>>
>>>> Thanks,
>>>>
>>>
>>> _______________________________________________
>>> linux-yocto mailing list
>>> linux-yocto at yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/linux-yocto
>>
>>
>>
>
>
> _______________________________________________
> linux-yocto mailing list
> linux-yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/linux-yocto
>