Re: Calling current() from interrupt context

[John Levon]

On Sun, 8 Oct 2000, Mitchell Blank Jr wrote:

> [EMAIL PROTECTED] wrote:
> > Looking at the code, I don't see any places where "current" is not valid.
> > Got some examples? 
> 
> It's not that its invalid, it just doesn't make much sense.  It points to
> whatever task happened to be running when the interrupt happened.  So
> any attempt to access it is 99% likely to be a bug.

FWIW, I use current->pid during an NMI interrupt for my statistical
profiler (currently only on P6 processors). This seems to be a
"reasonable" use of current() in an interrupt context (and it seems to
work 100% of the time ...)

So in this case, such an access makes perfect sense ...

john

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/