On Mon, Oct 09, 2000 at 02:20:27AM +0200, Andi Kleen wrote: > 2.4 TCP code relies on current being valid in a softirq. Well, then as long as Linux guarantees that there is always a valid 'current task' on a CPU, then I can special-case the called-from-interrupt case. The previous kernel stack pointer is accessible from another processor register, so I can go in there and pull it out and use it to calculate current. Is it possible to get an interrupt during context switching, for example? Or any other window during which there isn't a valid current? And what the hell does TCP need current for anyway? Later, Kenn - 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 interrup... Ralf Baechle
- Re: Calling current() from interrupt con... 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 con... Andi Kleen
- Re: Calling current() from interrup... Kenn Humborg
- Re: Calling current() from interrupt context Roman Zippel
- Re: Calling current() from interrupt context Francis Galiegue
- Re: Calling current() from interrupt context Linus Torvalds
- Re: Calling current() from interrupt context Keith Owens
- Re: Calling current() from interrupt context Kenn Humborg