Mark Rivers wrote:
Andrew Johnson wrote:
You will need to worry about more than one thread - each
different scan period has its own thread, so it just takes the user
changing
the SCAN field of the record for your code to have to call iopl(3) yet
again, and if it's set to Process Passive then there are several other
tasks that might be used depending on how the processing is initiated.
Actually, it's not that bad in my case. All of the actual I/O is done
by an MPF server task. Device support just sends messages to the MPF
server, so the tasks that process the record do not need iopl()
privilege.
I've got it working by calling iopl() in the MPF server task
initialization. It's not as clean as I'd like, because it requires some
#ifdef linux code, but it's OK.
I'd recommend calling ioperm() rather than iopl() since ioperm opens
only a specified window into the inp/outp space so you can't
accidentally tromp on some other (critical) port.
--
Eric Norum [email protected]
Advanced Photon Source Phone: (630) 252-4793
Argonne National Laboratory
- Replies:
- RE: Linux and EPICS threads John Quintana
- References:
- RE: Linux and EPICS threads Mark Rivers
- Navigate by Date:
- Prev:
RE: Linux and EPICS threads Mark Rivers
- Next:
RE: Linux and EPICS threads John Quintana
- 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: Linux and EPICS threads Mark Rivers
- Next:
RE: Linux and EPICS threads John Quintana
- 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
|