James Simmons writes:
> On Tue, 5 Oct 1999, Andreas Beck wrote:
>
> > Depends. If you have a good card, this is the way to go. If it cannot be
> > crashed/locked/burned by a bad program, all is well.
> >
> > If it can, we have to protect it.
>
> I agree. I think the best way is to create a struct mem_locks that has a
> linked list of locks to test and a field to discribe what card is using
> mmio thats mmapped to user space. Place this in the task_struct. In the
> schedular test to see if mem_lock is their then see if its lock by another
> process. If it is then skip picking this process.
There are easier ways to block a process than to modify the scheduler
itself. Check out the vt_waitactive code in drivers/char/vt.c and see
if that is ameniable to your problem.
Cheers,
__
\/ Andrew Apted <[EMAIL PROTECTED]>
