1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 <2010> 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 <2010> 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: 2 MAXv problems |
From: | "Steven M. Hartman" <[email protected]> |
To: | Eric Norum <[email protected]>, EPICS <[email protected]> |
Date: | Thu, 11 Mar 2010 12:57:12 -0500 |
"Don't block" and "don't alloc/free" certainly are necessary conditions for a routine to be ISR safe. But as you indicate there are a lot more things to worry about as well. Given the range of architectures and compilers with which EPICS can be used I really think that it's best to stick to routines that are explicitly described as safe. This is especially true given that calling a non-safe routine is likely to result in a system that fails very occasionally in a manner that would be very hard to debug.
Could someone with a more up to date version of the vxWorks manual check and see if there have been additions to the "safe" list since the very old manual from which I quoted?
-- Steven Hartman [email protected] || 865-466-6473
Library
bLib
errnoLib
eventLib
fppArchLib
intLib
intArchLib
logLib
lstLib
mathALib
msgQLib
rngLib
pipeDrv
selectLib
semLib
semPxLib
sigLib
taskLib
tickLib
tyLib
vxLib
wdLib