On Sun, Oct 08, 2000 at 05:05:45PM -0600, [EMAIL PROTECTED] wrote: > > > BTW: there is an implicit reference to "current" in smp_processor_id. > > > > Yes, on architectures that use current->processor that is an exception > > to the rule. After all, you know for sure that you're still on the > > same CPU as the task currently running. > > This makes sense. And I wish cpu architects would put a cpu-id > register somewhere > so that we could have fast computation of cpu-id on smp machines. For MIPS we use $28 aka $gp which MIPS in it's generosity just doesn't use for non-GP optimized code to point to current. That actually shaves of a few kb of the kernel size. From there on it's just one single machine instruction to get the cpuid which we could probably also hide in some of the rarely accessed MMU registers. Ralf - 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/
- Calling current() from interrupt context Kenn Humborg
- Re: Calling current() from interrupt context Jamie Lokier
- Re: Calling current() from interrupt context yodaiken
- Re: Calling current() from interrupt contex... Mitchell Blank Jr
- Re: Calling current() from interrupt co... yodaiken
- Re: Calling current() from interru... Mitchell Blank Jr
- Re: Calling current() from int... Ralf Baechle
- Re: Calling current() from interru... Ralf Baechle
- Re: Calling current() from interrupt co... John Levon
- Re: Calling current() from interrupt contex... Jamie Lokier
- Re: Calling current() from interrupt co... yodaiken
- Re: Calling current() from interrupt co... Kenn Humborg
- Re: Calling current() from interrupt contex... Ralf Baechle
- Re: Calling current() from interrupt context Andi Kleen
- Re: Calling current() from interrupt contex... Kenn Humborg
- Re: Calling current() from interrupt co... Andi Kleen
- Re: Calling current() from interrupt contex... Kenn Humborg
- Re: Calling current() from interrupt co... Andi Kleen