Re: Calling current() from interrupt context

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Mon Oct 09 2000 - 18:30:50 EDT

Next message: Alan Cox: "Re: MAX iso9660 size?"

Previous message: Linus Torvalds: "test10-pre1"
In reply to: Kenn Humborg: "Re: Calling current() from interrupt context"
Next in thread: Andi Kleen: "Re: Calling current() from interrupt context"
Next in thread: Ralf Baechle: "Re: Calling current() from interrupt context"
Reply: Andi Kleen: "Re: Calling current() from interrupt context"
Reply: Linus Torvalds: "Re: Calling current() from interrupt context"
Reply: yodaiken@fsmlabs.com: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> 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

-
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/

Next message: Alan Cox: "Re: MAX iso9660 size?"
Previous message: Linus Torvalds: "test10-pre1"
In reply to: Kenn Humborg: "Re: Calling current() from interrupt context"
Next in thread: Andi Kleen: "Re: Calling current() from interrupt context"
Next in thread: Ralf Baechle: "Re: Calling current() from interrupt context"
Reply: Andi Kleen: "Re: Calling current() from interrupt context"
Reply: Linus Torvalds: "Re: Calling current() from interrupt context"
Reply: yodaiken@fsmlabs.com: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Oct 09 2000 - 18:39:40 EDT