Date: Tue, 1 Oct 2002 16:10:19 -0400 (EDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_synch.c Message-ID: <200210012010.g91KAJ3B052944@khavrinen.lcs.mit.edu> In-Reply-To: <Pine.NEB.3.96L.1021001111753.32141A-100000@fledge.watson.org> References: <200210011410.g91EA9EZ026286@freefall.freebsd.org> <Pine.NEB.3.96L.1021001111753.32141A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Tue, 1 Oct 2002 11:24:07 -0400 (EDT), Robert Watson <rwatson@FreeBSD.org> said: > Yeah, the notion of signals and threads is still a bit cloudy in my mind. POSIX makes this quite clear: # At the time of generation, a determination shall be made whether the # signal has been generated for the process or for a specific thread # within the process. Signals which are generated by some action # attributable to a particular thread, such as a hardware fault, shall # be generated for the thread that caused the signal to be # generated. Signals that are generated in association with a process # ID or process group ID or an asynchronous event, such as terminal # activity, shall be generated for the process. See the System Interfaces volume of 1003.1-2001, section 2.4, for a complete discussion of signal delivery. (Note that the POSIX threading model is not the only one possible, and we may wish to provide for more general signal delivery.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210012010.g91KAJ3B052944>