Hi, > The m68k port which has a interrupt stack solves the problem by > loading current into a global register variable on all kernel entries. Not all m68k cpus have an interrupt stack and it can be turned off, so we don't use it. bye, Roman - 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 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
- Re: Calling current() from interrupt context Alan Cox
- Re: Calling current() from interrupt con... Andi Kleen
- Re: Calling current() from interrup... Alan Cox
- Re: Calling current() from inte... Andi Kleen
- Re: Calling current() from inte... David S. Miller
- Re: Calling current() from inte... Jeff V. Merkey