> problem Ulrich mentioned - it splits up ->user_tid into ->set_child_tid
> and ->clear_child_tid pointers. This way the clearing and setting
> functionality is cleanly separated.
How about making ->set_child_tid a parameter for schedule_tail, or even
directly using it in the ret_from_fork assembly?
It doesn't make much sense to have a variable in task_struct which is
used only at task creation.
--=-FbiN7rpTcwVZbqL+bp2X
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQA92KTTdjkty3ft5+cRAjf8AKCeaUw8ZBQHH/fNNcHEBRC+wKOlmQCeK70V
hVPx7UBRBhNA2x5kDF2+PAU=
=BV67
-----END PGP SIGNATURE-----
--=-FbiN7rpTcwVZbqL+bp2X--
-
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/