On Mon, 9 Oct 2000, Alan Cox wrote: > > I think I'll go for the 'current is in a well-known register' > > approach and see how this goes... > > Failing that the 2.0 approach will work, current is a global in uniprocessor > and a #define to an array indexed by cpu id in smp You can also still do the stack pointer plaything by just using indirection: and when you context switch you switch the pointer around at the base of the per-cpu interrupt stack. Linus - 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 inter... Andi Kleen
- Re: Calling current() from inter... David S. Miller
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Jeff V. Merkey
- Re: Calling current() from inter... Alan Cox
- Re: Calling current() from interrupt... Kenn Humborg
- Re: Calling current() from inter... Andi Kleen
- Re: Calling current() from inter... Kenn Humborg
- Re: Calling current() from interrupt cont... Linus Torvalds
- Re: Calling current() from interrupt... Jamie Lokier
- Re: Calling current() from inter... Alan Cox
- Re: Calling current() from inter... David S. Miller
- Re: Calling current() from inter... kumon
- Re: Calling current() from inter... Linus Torvalds
- Re: Calling current() from interrupt cont... yodaiken
- Re: Calling current() from interrupt context Ralf Baechle