Re: FW: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Philippe Gerum via Xenomai
On 5/14/19 12:40 PM, Lange Norbert wrote: > What do you think about this hackaround? > Still not "clean" to call in a signal handler but it does work. Yes, this is documented as such in backtrace() as the recommended work around for this situation. I would add this stuff to install_sigshadow() ins

Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Philippe Gerum via Xenomai
On 5/14/19 12:24 PM, Lange Norbert wrote: > > >> -Original Message- >> From: Philippe Gerum >> Sent: Dienstag, 14. Mai 2019 12:05 >> To: Lange Norbert ; Xenomai >> (xenomai@xenomai.org) >> Subject: Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from >> atfork() handlers >> >

FW: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Lange Norbert via Xenomai
e not an intended recipient, you are hereby notified that you received this email in error and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system. ANDRITZ HYDRO GmbH Rechtsform/ Legal form: Gesellschaft mit beschränkter Haftung / Corporation Firmensitz/ Registered seat: Wien Firmenbuchgericht/ Court of registry: Handelsgericht Wien Firmenbuchnummer/ Company registration: FN 61833 g DVR: 0605077 UID-Nr.: ATU14756806 Thank You -- next part -- A non-text attachment was scrubbed... Name: 0001-libcobalt-resolve-backtrace-early.patch Type: application/octet-stream Size: 1018 bytes Desc: 0001-libcobalt-resolve-backtrace-early.patch URL: <http://xenomai.org/pipermail/xenomai/attachments/20190514/6b6aa20a/attachment.obj>

RE: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Lange Norbert via Xenomai
> -Original Message- > From: Philippe Gerum > Sent: Dienstag, 14. Mai 2019 12:05 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) > Subject: Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from > atfork() handlers > > E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASU

Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Philippe Gerum via Xenomai
On 5/14/19 11:53 AM, Lange Norbert wrote: > (readding ML) > >> -Original Message- >> From: Philippe Gerum >> Sent: Dienstag, 14. Mai 2019 10:38 >> To: Lange Norbert >> Subject: Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from >> atfork() handlers >> >> E-MAIL FROM A NON-AN

RE: [PATCH] lib/cobalt: init: do not call pthread_atfork() from atfork() handlers

2019-05-14 Thread Lange Norbert via Xenomai
(readding ML) > -Original Message- > From: Philippe Gerum > Sent: Dienstag, 14. Mai 2019 10:38 > To: Lange Norbert > Subject: Re: [PATCH] lib/cobalt: init: do not call pthread_atfork() from > atfork() handlers > > E-MAIL FROM A NON-ANDRITZ SOURCE: AS A SECURITY MEASURE, PLEASE > EXERCISE

Re: Large ToD drift with clocktest

2019-05-14 Thread Jan Kiszka via Xenomai
On 14.05.19 11:15, Bart Vissers wrote: Thanks for looking into it! Actually, we are transitioning from Xenomai 2 to 3 and we're facing Ethercat Distributed Clocks (DC) synchronization issues. The old OS with Xenomai 2 can run DC in both Master Shift and Bus Shift mode. With the 4.14 kernel and Xe

Re: Large ToD drift with clocktest

2019-05-14 Thread Bart Vissers via Xenomai
Thanks for looking into it! Actually, we are transitioning from Xenomai 2 to 3 and we're facing Ethercat Distributed Clocks (DC) synchronization issues. The old OS with Xenomai 2 can run DC in both Master Shift and Bus Shift mode. With the 4.14 kernel and Xenomai 3, Bus Shift doesn't work due to to

Re: numa stress test - Intel j1900

2019-05-14 Thread Jan Kiszka via Xenomai
On 10.05.19 14:51, Stéphane Ancelot via Xenomai wrote: Hi guys, I would like to know if some people have already done some of NUMA stress tests with multi core and xenomai. I have a problem with an Intel  j1900 cpu, in which under heavy X11 usage , I have large latency between tasks breaking re

Re: Large ToD drift with clocktest

2019-05-14 Thread Jan Kiszka via Xenomai
On 13.05.19 18:41, Bart Vissers via Xenomai wrote: Hi all, When running clocktest I get the following output: $ /usr/xenomai/bin/clocktest == Testing built-in CLOCK_REALTIME (0) CPU ToD offset [us] ToD drift [us/s] warps max delta [us] --- ---