On Mon, Oct 09, 2000 at 11:30:50PM +0100, 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 The problem is where to get the cpuid from (see how smp_processor_id is currently defined ;) When you don't have a hidden register in the CPU you're screwed. [x86-64 has one btw] -Andi - 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 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
- Re: Calling current() from inte... Jeff V. Merkey
- Re: Calling current() from inte... Jeff V. Merkey
- Re: Calling current() from inte... Jeff V. Merkey
- Re: Calling current() from inte... Alan Cox
- Re: Calling current() from interrup... Kenn Humborg
- Re: Calling current() from inte... Andi Kleen