siginfo(3): Document SI_USER and SI_KERNEL signal codes.

MFC after:	1 week

1 files changed, 23 insertions, 2 deletions

diff --git a/share/man/man3/siginfo.3 b/share/man/man3/siginfo.3
index 9452b08..f711653 100644
--- a/share/man/man3/siginfo.3
+++ b/share/man/man3/siginfo.3
@@ -27,7 +27,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd December 8, 2005
+.Dd September 14, 2012
 .Dt SIGINFO 3
 .Os
 .Sh NAME
@@ -195,6 +195,8 @@ signal generated by expiration of a timer set by
 signal generated by completion of an asynchronous I/O request
 .It Ta Dv SI_MESGQ Ta
 signal generated by arrival of a message on an empty message queue
+.It Ta Dv SI_KERNEL Ta
+signal generated by miscellaneous parts of the kernel
 .El
 .Pp
 In addition, the following signal-specific information is available:
@@ -235,6 +237,10 @@ or
 Finally, the following code-specific information is available:
 .Bl -column ".Dv SI_QUEUE" ".Va si_overrun"
 .It Sy "Code	Member	Value"
+.It Dv SI_USER Ta Va si_pid Ta
+the process ID that sent the signal
+.It Ta Va si_uid Ta
+real user ID of the process that sent the signal
 .It Dv SI_QUEUE Ta Va si_value Ta
 the value passed to
 .Xr sigqueue 2
@@ -277,6 +283,14 @@ signal is queued when a process changed its status or exited.
 .Tn POSIX
 Realtime Extensions like aio, timer, and message queue also queue
 signals.
+Signals with code
+.Dv SI_USER
+or
+.Dv SI_KERNEL
+are only queued if there are sufficient resources;
+otherwise,
+.Dv SI_NOINFO
+results.
 For some hardware architectures, the exact value of
 .Va si_addr
 might not be available.
@@ -289,7 +303,8 @@ might not be available.
 .Xr sigwaitinfo 2 ,
 .Xr timer_create 2 ,
 .Xr timer_settime 2 ,
-.Xr waitpid 2
+.Xr waitpid 2 ,
+.Xr pthread_kill 3
 .Sh STANDARDS
 The
 .Vt siginfo_t
@@ -300,6 +315,12 @@ Full support for
 .Tn POSIX
 signal information first appeared in
 .Fx 7.0 .
+The codes
+.Dv SI_USER
+and
+.Dv SI_KERNEL
+can be generated as of
+.Fx 8.1 .
 .Sh AUTHORS
 This manual page was written by
 .An "David Xu" Aq davidxu@FreeBSD.org .