Re:

george anzinger
2001-05-08T21:34:01Z

"Richard B. Johnson" wrote:
>
> To driver wizards:
>
> I have a driver which needs to wait for some hardware.
> Basically, it needs to have some code added to the run-queue
> so it can get some CPU time even though it's not being called.
>
> It needs to get some CPU time which can be "turned on" or
> "turned off" as a result of an interrupt or some external
> input from an ioctl().
>
> So I thought that the "tasklet" would be ideal. However, the
> scheduler "thinks" that a tasklet is an interrupt, so any
> attempt to sleep in the tasklet results in a kernel panic,
> "ieee scheduling in an interrupt..., BUG sched.c line 688".
>
> Next, I added code to try queue_task(). This has the same problem.
>
> Basically the procedure needs to do:
>
> procedure()
> {
> if(some_event)
> schedule_timeout(n); /* Needs to sleep */
> else if(something_else)
> do_something();
> queue_task(procedure, &tq_immediate); /* Needs to queue itself again */
> }
>
> Since I'm running against a time-line, I temporarily gave the module
> some CPU time through an ioctl(), i.e., a separate task that does nothing
> except repeatably execute ioctl(GIVE_CPU, NULL); This shows that the
> driver actually works. It's a GPIB driver so it needs to get the
> CPU to find out if it's addressed to listen, etc. These events don't
> produce interrupts.
>
> So, what am I supposed to do to add a piece of driver code to the
> run queue so it gets scheduled occasionally?
>
> Cheers,
> Dick Johnson

How about something like:

#include <linux/timer.h>

void queue_task(void process_timeout(void), unsigned long timeout,
struct timer_list *timer, unsigned long data)
{
unsigned long expire = timeout + jiffies;

init_timer(&timer);
timer->expires = expire;
timer->data = data;
timer->function = process_timeout;

add_timer(&timer);
}

You will have to define the "struct timer_list timer". This should
cause the function passed to be called after "timeout" jiffies (1/HZ,
not to be confused with 10 ms). If you want to stop the timer early do:

del_timer_sync(&timer);

"data" was not used in you example, but process_timeout will be passed
"data" when it is called. This routine is called as part of the timer
interrupt, so it must be fast and should not do schedule() calls. It
could queue a tasklet, however, to relax constraints a bit.

George