[lttng-dev] LTTng - Xenomai : different results between timestamp-lttng and rt_time_read()
nolange79 at gmail.com
Tue May 25 04:46:35 EDT 2021
Am Fr., 21. Mai 2021 um 12:13 Uhr schrieb MONTET Julien
<julien.montet at reseau.eseo.fr>:
> Hello Mathieu, Norbert and Jan,
> Thank you for all of your explainations and the overview of the system.
> No I didn't change the ipipe patch for the vDSO, I may try this.
> If I have correctly understood, this patch prevents Cobalt from entering in a deadlock when the kernel is using the vDSO and the program interrupts the kernel at the same time. On which kernel does it word (aroubd 4.19) ?
> I currently try to avoid kernel 5.4 because I remember I faced some boot issues (but it is on another topic).
That patch was for 4.19 AFAIR, but its specific to x86. The Linux
kernel cleaned up the vdso handling to have a common base with some
but back then its been separate for each arch
> Here the issues i faced (drawn on TraceCompass). Are these the deadlocks we are talking about ?
> https://postimg.cc/BP4G3bF0 (on 11:02:56:380)
Nope, if you get such a deadlock, then your only hope is Xenomai's
Watchdog killing the process.
It should happen very rarely (but thats not an argument if your
software should run for years).
More information about the lttng-dev