On May 31, 2012, at 9:17 AM, Andrew Johnson wrote:
>>
>
> You wrote "device support interrupt callback or read method", which I
> originally read as the ISR, but it would be just as bad to set the TIME field
> in the port thread or a callback routine without first locking the lockset.
>
> If you meant that TIME gets set by the dset->read_xxx() routine then that's
> fine, because it gets called by the record's process routine with the lockset
> locked. I wasn't really thinking about the limitations of interrupt context,
> it's that accessing a record's fields from any thread that has not first
> locked the record's lockset is not safe.
Right -- the actual setting of the .TIME field is done by the various devEpics dset->read_xxx() routines.
Sorry to have implied anything different.
- References:
- Proposed change in asyn - request for comments Mark Rivers
- Re: Proposed change in asyn - request for comments Andrew Johnson
- Re: Proposed change in asyn - request for comments Eric Norum
- Re: Proposed change in asyn - request for comments Andrew Johnson
- Navigate by Date:
- Prev:
Re: Proposed change in asyn - request for comments Andrew Johnson
- Next:
waveform of STRING memory structure Pavel Masloff
- 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
- Navigate by Thread:
- Prev:
Re: Proposed change in asyn - request for comments Andrew Johnson
- Next:
Re: Proposed change in asyn - request for comments Bruce Hill
- 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
|