Attach a handler function to a pulse code
#include <sys/iofunc.h> #include <sys/dispatch.h> int pulse_attach( dispatch_t * dpp, int flags, int code, int (* func) ( message_context_t * ctp, int code, unsigned flags, void * handle ), void * handle );
libc
Use the -l c option to qcc to link against this library. This library is usually included automatically.
The pulse_attach() function attaches a pulse code to a user-supplied function func. You can use the same function func with message_attach(). By examining ctp->rcvid, the func function can determine whether a pulse or message was received.
When the resource manager receives a pulse that matches code, it calls func. This user-supplied function is responsible for doing any specific work needed to handle the pulse pointed to by ctp->msg.pulse. The handle passed to the function is the handle initially passed to pulse_attach(). The handle may be a device entry you want associated with the pulse code. Your function should return 0; other return values are reserved.
You typically use pulse_attach() to associate pulses generated by interrupt handlers or timers with a routine in the main program of your resource manager.
If MSG_FLAG_ALLOC_PULSE is specified, the function returns the allocated pulse code; otherwise, it returns the code that's passed in. On failure, -1 is returned (errno is set).
#include <sys/dispatch.h> #include <time.h> #include <stdio.h> #include <stdlib.h> int my_func( … ) { … } int main( int argc, char **argv ) { dispatch_t *dpp; int flag = 0, code, mycode; if ( ( dpp = dispatch_create() ) == NULL ) { fprintf( stderr, "%s: Unable to allocate \ dispatch handle.\n",argv[0] ); return EXIT_FAILURE; } … mycode = …; if ( (code = pulse_attach( dpp, flag, mycode, &my_func, NULL)) == -1 ) { fprintf ( stderr, "Failed to attach code %d.\n", mycode ); return 1; } /* else successfully attached a pulse code */ … }
For examples using the dispatch interface, see dispatch_create(), message_attach(), resmgr_attach(), and thread_pool_create().
Safety: | |
---|---|
Cancellation point | Yes |
Interrupt handler | No |
Signal handler | No |
Thread | Yes |
message_attach(), pulse_detach()
“Layers in a resource manager” in the Bones of a Resource Manager chapter of Writing a Resource Manager