Linus Torvalds wrote: > 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. Indirection, à la "current = *(stack & ~8191)" might not be a bad idea in general. As Ralf Baechle noted, having all the task structs at the same offset isn't good for the cache. -- Jamie - 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... 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