Of course, that'll leave one thread blocked in io_devctl, potentially forever.

You might want to send a signal to the other thread, cancel it, or not do anything blocking in there in the first place.
 What operation is your devctl thread blocked on? What is it waiting for?


----- Originalnachricht -----
Von: David Sarrazin [mailto:community-noreply@qnx.com]
Gesendet: Friday, August 10, 2012 10:40 AM
An: ostech-core_os@community.qnx.com <ostech-core_os@community.qnx.com>
Betreff: RE: TimerTimeout() not getting timeout

Simplest way to is to MsgError(ctp->rcvid), which will unblock the client.  It's then very important for your resource 
manager to keep track of the fact that it has already replied, and either abort the current operation, or simply skip 
over the MsgReply that happens when the devctl thread finishes.

> -----Original Message-----
> From: Fraser Moore [mailto:community-noreply@qnx.com]
> Sent: August-10-12 10:39 AM
> To: ostech-core_os@community.qnx.com
> Subject: Re: TimerTimeout() not getting timeout
> 
> I can now get io_unblock to be called from a separate thread but how do I
> then reply to the client which is blocked on another thread to unblock it?
> 
> cheers,
> fraser
> 
> On 10/08/2012 10:43, Thomas Haupt wrote:
> > Hi Fraser,
> >
> > sure, feel free.
> >
> > Cheers,
> > Thomas
> >
> > -----Original Message-----
> > From: Fraser Moore [mailto:community-noreply@qnx.com]
> > Sent: Freitag, 10. August 2012 10:37
> > To: ostech-core_os@community.qnx.com
> > Subject: Re: TimerTimeout() not getting timeout
> >
> > Hi Thomas,  I think that's exactly what's happening.  I had just been reading
> the about this in the documentation.  I will try and create a new thread to
> handle this.
> >
> > I may be back for more advice.
> >
> > Thanks,
> > Fraser
> >
> > On 10/08/2012 09:25, Thomas Haupt wrote:
> >> The io_unblock callout will only be invoked when you get back to your
> resource manager's main loop (dispatch_block() / dispatch_handle())
> somehow.
> >>
> >> If you are handling the devctl in some way such that the resource
> manager will still be in io_devctl() when the timeout comes, no unblock
> handling will be done.
> >>
> >> In order for unblocking to work properly, you need to somehow put
> "long" (potentially blocking) tasks into the  "background" and return to the
> main message handler loop. That could mean doing them in a separate
> thread, or adding entries on an "outstanding tasks" list that you can look into
> when you see a state change (e.g., an interrupt signaling data coming in).
> >>
> >> Regards,
> >> Thomas
> >>
> >> -----Original Message-----
> >> From: Fraser Moore [mailto:community-noreply@qnx.com]
> >> Sent: Freitag, 10. August 2012 09:44
> >> To: ostech-core_os@community.qnx.com
> >> Subject: Re: TimerTimeout() not getting timeout
> >>
> >> I tried defining my own io_unblock that simply calls
> iofunc_unblock_default().  However I never see this function getting called
> by the resource manager.  I am new to writing resource managers so what
> should I be doing to handle unblocks?
> >>
> >> cheers,
> >> fraser
> >>
> >> On 09/08/2012 14:52, Lichun Zhu wrote:
> >>> I think this is it, the resmgr did not handle unblock.
> >>>
> >>> -----Original Message-----
> >>> From: Thomas Haupt [mailto:community-noreply@qnx.com]
> >>> Sent: Thursday, August 09, 2012 9:44 AM
> >>> To: 'ostech-core_os@community.qnx.com'
> >>> Subject: RE:...

Ideally if this is a single threaded resmgr, the devctl handler should not block if it's waiting for something say there
 is no data available at the time, then save the ctp->rcvid for later reply and return _RESMGR_NOREPLY, then you don't 
have to create another thread for that.


> -----Original Message-----
> From: David Sarrazin [mailto:community-noreply@qnx.com]
> Sent: August-10-12 10:41 AM
> To: ostech-core_os@community.qnx.com
> Subject: RE: TimerTimeout() not getting timeout
> 
> Simplest way to is to MsgError(ctp->rcvid), which will unblock the client.  It's
> then very important for your resource manager to keep track of the fact that it
> has already replied, and either abort the current operation, or simply skip over
> the MsgReply that happens when the devctl thread finishes.
> 
> > -----Original Message-----
> > From: Fraser Moore [mailto:community-noreply@qnx.com]
> > Sent: August-10-12 10:39 AM
> > To: ostech-core_os@community.qnx.com
> > Subject: Re: TimerTimeout() not getting timeout
> >
> > I can now get io_unblock to be called from a separate thread but how
> > do I then reply to the client which is blocked on another thread to unblock it?
> >
> > cheers,
> > fraser
> >
> > On 10/08/2012 10:43, Thomas Haupt wrote:
> > > Hi Fraser,
> > >
> > > sure, feel free.
> > >
> > > Cheers,
> > > Thomas
> > >
> > > -----Original Message-----
> > > From: Fraser Moore [mailto:community-noreply@qnx.com]
> > > Sent: Freitag, 10. August 2012 10:37
> > > To: ostech-core_os@community.qnx.com
> > > Subject: Re: TimerTimeout() not getting timeout
> > >
> > > Hi Thomas,  I think that's exactly what's happening.  I had just
> > > been reading
> > the about this in the documentation.  I will try and create a new
> > thread to handle this.
> > >
> > > I may be back for more advice.
> > >
> > > Thanks,
> > > Fraser
> > >
> > > On 10/08/2012 09:25, Thomas Haupt wrote:
> > >> The io_unblock callout will only be invoked when you get back to
> > >> your
> > resource manager's main loop (dispatch_block() / dispatch_handle())
> > somehow.
> > >>
> > >> If you are handling the devctl in some way such that the resource
> > manager will still be in io_devctl() when the timeout comes, no
> > unblock handling will be done.
> > >>
> > >> In order for unblocking to work properly, you need to somehow put
> > "long" (potentially blocking) tasks into the  "background" and return
> > to the main message handler loop. That could mean doing them in a
> > separate thread, or adding entries on an "outstanding tasks" list that
> > you can look into when you see a state change (e.g., an interrupt signaling
> data coming in).
> > >>
> > >> Regards,
> > >> Thomas
> > >>
> > >> -----Original Message-----
> > >> From: Fraser Moore [mailto:community-noreply@qnx.com]
> > >> Sent: Freitag, 10. August 2012 09:44
> > >> To: ostech-core_os@community.qnx.com
> > >> Subject: Re: TimerTimeout() not getting timeout
> > >>
> > >> I tried defining my own io_unblock that simply calls
> > iofunc_unblock_default().  However I never see this function getting
> > called by the resource manager.  I am new to writing resource managers
> > so what should I be doing to handle unblocks?
> > >>
> > >> cheers,
> > >> fraser
> > >>
> > >> On 09/08/2012...