Experimental Physics and Industrial Control System
Ok, maybe time to take a(nother) step back and ask if epicsMutexPriorityInversionTest should be run by default.
> testOk1( hiPriStalledTimeUs < 1000 );
This will almost certainly fail randomly with the CI builders since they don't have a PREEMPT_RT kernel, and are anyway timeshare VMs.
I don't see a need for Base to test whether PTHREAD_PRIO_INHERIT functions correctly. This seems like testing malloc(). The critical question which a user will have is whether PTHREAD_PRIO_INHERIT is being set. This seems more like asking whether OS priorities are being set at all. This is complicated since, unlike priority or mlock(), I don't know of a straightforward way to verify this externally. (I would resort to strace, which is complicated to interpret)
The question of OS priorities is answered by epicsThreadShowAll(). So maybe it would be sufficient for epicsMutexShowAll() to print a line showing if PTHREAD_PRIO_INHERIT is being set?
--
https://code.launchpad.net/~dirk.zimoch/epics-base/+git/epics-base/+merge/394327
Your team EPICS Core Developers is subscribed to branch epics-base:7.0.
- Navigate by Date:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 mdavidsaver via Core-talk
- Next:
[Bug 1913699] Re: vxWorks compilation fails with undeclared function Andrew Johnson via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 mdavidsaver via Core-talk
- Next:
Re: [Merge] ~dirk.zimoch/epics-base:epicsMutexPriorityInheritance into epics-base:7.0 Dirk Zimoch via Core-talk
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
<2021>
2022
2023
2024