On Sun, Oct 08, 2000 at 04:36:09PM -0600, [EMAIL PROTECTED] wrote: > Looking at the code, I don't see any places where "current" is not valid. > Got some examples? More a design principle than a real problem. > BTW: there is an implicit reference to "current" in smp_processor_id. Which is valid because the process the current variable is pointing to is always running on the current CPU, therefore it's implicitly locked and can't just go away. Due to the existence of the idle process there is also a guarantee that current always points to a valid process. Not much guarantee of anything else for the current process - it might just be exiting for example. Ralf - 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/
- Re: Calling current() from interrupt context yodaiken
- Re: Calling current() from interrupt context Mitchell Blank Jr
- Re: Calling current() from interrupt context yodaiken
- Re: Calling current() from interrupt contex... Mitchell Blank Jr
- Re: Calling current() from interrupt co... Ralf Baechle
- Re: Calling current() from interrupt contex... Ralf Baechle
- Re: Calling current() from interrupt context John Levon
- Re: Calling current() from interrupt context Jamie Lokier
- Re: Calling current() from interrupt context yodaiken
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Ralf Baechle
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt contex... Andi Kleen
- Re: Calling current() from interrupt co... Kenn Humborg
- Re: Calling current() from interrupt context Roman Zippel