Re: [Xenomai] kernel does not boot when ipipe tracer is activated

2018-03-14 Thread Yann le Chevoir
Hi, I have the same problem Cédric had in November. @Cédric, did you manage to activate ipipe-tracer on your iMX6? Even with earlyprintk (menuconfig and bootargs), the kernel hangs to "Starting kernel...". I have an iMX6 too, my Kernel is 4.1.38. The I-pipe patch 4.1.18 did not exactly fit. I fi

Re: [Xenomai] Latency Peaks with Skylake vs. Haswell

2018-03-14 Thread Schrenkhammer, Martin
To be honest, I don't know how exactly tracking this. What I am doing: Open 1 terminal window which runs latency test. With second terminal window I watch -n1 cat /proc/interrupts During idle (beside latency test and watching interrupts), there are about 20 MSI / sec. If another window (e.g. Fil

Re: [Xenomai] [PATCH] cobalt/thread: Move tcb clearing into __xnthread_init

2018-03-14 Thread Philippe Gerum
On 03/08/2018 04:55 PM, Jan Kiszka wrote: > From: Jan Kiszka > > This both de-duplicates the code and ensures that all fields are zeroed > prior to calling one of the actual tcb initialization functions. > Specifically if host_task is not properly cleaned, we may cause a bug > when using the fiel

Re: [Xenomai] Latency Peaks with Skylake vs. Haswell

2018-03-14 Thread Philippe Gerum
On 03/13/2018 12:33 PM, Schrenkhammer, Martin wrote: > I am currently porting a project from Haswell to Skylake (i5-6440EQ). When in > desktop, I observe latency peaks when windows are moved around or zoomed. > With Haswell CPUs, there is not impact of graphic workload. Unfortunately > everythin

Re: [Xenomai] Strange behaviour after calling clock_settime

2018-03-14 Thread Julien Blanc
Le mercredi 14 mars 2018 à 12:00 +0100, Philippe Gerum a écrit : > On 03/14/2018 11:42 AM, Julien Blanc wrote: > > > > Hi, > > > > The current xenomai documentation states that it is allowed to call > > clock_settime with CLOCK_REALTIME parameter to set the value of the > > xenomai realtime clock

Re: [Xenomai] Strange behaviour after calling clock_settime

2018-03-14 Thread Philippe Gerum
On 03/14/2018 11:42 AM, Julien Blanc wrote: > Hi, > > The current xenomai documentation states that it is allowed to call > clock_settime with CLOCK_REALTIME parameter to set the value of the > xenomai realtime clock. On our board, the value at bootup is always 0 Assuming you run in dual kernel m

[Xenomai] Strange behaviour after calling clock_settime

2018-03-14 Thread Julien Blanc
Hi, The current xenomai documentation states that it is allowed to call clock_settime with CLOCK_REALTIME parameter to set the value of the xenomai realtime clock. On our board, the value at bootup is always 0 (so, epoch), despite the hardware clock being correctly set. However, we experience bad