Subject: Re: Locking primitives kernel only?
To: None <email@example.com>
From: Chuck Silvers <firstname.lastname@example.org>
Date: 05/02/2000 13:20:48
in particular, if an interrupt handler needs to acquire a spinlock,
curproc might be NULL. we can't use a thread id to identify a spinlock owner
since we don't have interrupt threads.
> However, using curproc as the identifier for a simplelock is incorrect,
> as simplelocks are owned by CPUs, not by processes. Processes own
> sleep locks implemented by lockmgr().
> -- Jason R. Thorpe <email@example.com>