Joe deBlaquiere wrote:
>
> Maybe I've been off in the hardware lab for too long, but how about
>
> 1. using ioperm to give access to the parallel port.
> 2. have your program write a byte (thread id % 256 ?) constantly to the
> port during it's other activity
> 3. capture the results from another computer with an ecp port
>
> This way you don't run the risk of altering the scheduler behavior with
> your logging procedure.
It's a technique I've used in debugging realtime systems. It works
great, but bear in mind that the out to the parallel port costs an awful
lot of cycles. You *will* alter the behaviour of the scheduler.
-- Daniel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jan 31 2001 - 21:00:18 EST