Re: Calling current() from interrupt context

From: Roman Zippel (zippel@fh-brandenburg.de)
Date: Mon Oct 09 2000 - 04:34:19 EST

Next message: Andre Hedrick: "Re: Newer motherboards / CPU's / hardware with Linux"
Previous message: Jorg de Jong: "Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?"
In reply to: Andi Kleen: "Re: Calling current() from interrupt context"
Next in thread: Francis Galiegue: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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 majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Next message: Andre Hedrick: "Re: Newer motherboards / CPU's / hardware with Linux"
Previous message: Jorg de Jong: "Re: will ip 6 in ip4 tunnelling be fixed anytime soon ?"
In reply to: Andi Kleen: "Re: Calling current() from interrupt context"
Next in thread: Francis Galiegue: "Re: Calling current() from interrupt context"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:11 EST