Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK

From: Linus Torvalds (torvalds@transmeta.com)
Date: Tue Aug 13 2002 - 13:41:45 EST

Next message: Linus Torvalds: "Re: [PATCH] Network Options and Network Devices together"
Previous message: Randy.Dunlap: "[PATCH] Network Options and Network Devices together"
In reply to: Ingo Molnar: "[patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Next in thread: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Reply: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Reply: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 13 Aug 2002, Ingo Molnar wrote:
>
> CLONE_SETTLS => if present then the third clone() syscall parameter
> is the new TLS.
>
> CLONE_SETTID => if present then the child TID is written to the
> address specified by the fourth clone() parameter.

Except you actually test the CLONE_SETTLS bit..

This looks basically ok, although that "struct thread_struct *t" still
serves no useful purpose..

Linus

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Linus Torvalds: "Re: [PATCH] Network Options and Network Devices together"
Previous message: Randy.Dunlap: "[PATCH] Network Options and Network Devices together"
In reply to: Ingo Molnar: "[patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Next in thread: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Reply: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Reply: Ingo Molnar: "Re: [patch] CLONE_SETTLS, CLONE_SETTID, 2.5.31-BK"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu Aug 15 2002 - 22:00:33 EST