Messages in this thread |  | | Date | Mon, 9 Oct 2000 02:14:47 +0100 | From | Kenn Humborg <> | Subject | Re: Calling current() from interrupt context |
| |
On Mon, Oct 09, 2000 at 01:02:21AM +0200, Jamie Lokier wrote: > yodaiken@fsmlabs.com wrote: > > BTW: there is an implicit reference to "current" in smp_processor_id. > > Yes I forgot about that. (Self-flagellate). However that is > architecture specific. If it's not an SMP Vax port, no big deal. If it > is, there's a way to arrange that smp_processor_id returns the correct > processor id even from the interrupt stack.
Yes, that's easily done. Interrupt stacks are per-processor, so they are part of the per-cpu data structures. So we can use a similar trick to the task_struct/kernel stack hack. (And still get a crash if current is used from interrupt context.)
Later, Kenn
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |