
Notes on kernel monitoring
---------------------------------------

- only 1 app can take over the kernel event mechanism at 1 time. The last to
  takeover will be the active one.

- use shared memory. The event logging is non-blocking, based on software
  interrupts.
  If you use a mechanism like a proxy (see 'kertest.c') then be sure to
  run at high enough priority that you do not lose events. Or better yet,
  use a simple mechanism in shared memory to buffer events as they come in
  and pull them off as you need them.


The examples:

simple1:    prints out process/vc/proxy creation events

kertest:    prints out creation and death events, as well as gets current
            process table.

imon:       a more complete example showing how you can accumulate event
            logging. It stores interrupt and priority times.
            Use 'syst' to print out the shared memory that imon logs to.


Special Note!!!
---------------------
the files 'qssl' and 'qssl.ind' should be copied to /usr/lib/msgs 
you can see the usage of this data in the lookup.c file.

