Re: [Xenomai] Strange scheduling behaviour

2017-11-23 Thread Philippe Gerum
On 11/23/2017 03:35 PM, Cédric Perles wrote: >>> Hi, >>> >>> I’m working on an iMX6 based board with NXP kernel 4.1.15. > >>> Vendor kernels for i.MX6 are creepy (another vowel comes to mind). A >>> recent mainline kernel is just fine if the SoC supports it. If not, >>> porting the SoC (and/or

Re: [Xenomai] Strange scheduling behaviour

2017-11-23 Thread Cédric Perles
>> Hi, >> >> I’m working on an iMX6 based board with NXP kernel 4.1.15. >> Vendor kernels for i.MX6 are creepy (another vowel comes to mind). A >> recent mainline kernel is just fine if the SoC supports it. If not, >> porting the SoC (and/or missing driver) to mainline is often much > >>

Re: [Xenomai] Strange scheduling behaviour

2017-11-22 Thread Philippe Gerum
On 11/22/2017 05:10 PM, Cédric Perles wrote: > Hi, > > I’m working on an iMX6 based board with NXP kernel 4.1.15. Vendor kernels for i.MX6 are creepy (another vowel comes to mind). A recent mainline kernel is just fine if the SoC supports it. If not, porting the SoC (and/or missing driver) to

[Xenomai] Strange scheduling behaviour

2017-11-22 Thread Cédric Perles
Hi, I’m working on an iMX6 based board with NXP kernel 4.1.15. I would like to understand why latency max returned by cyclictest increases from 20µs to 100µs when dohell accesses to USB. Since i-pipe tracer refuses to work, I used ftrace to record cobalt, scheduling and irq events. Here is what