Konstantin Belousov 5c7bebf961 The process spin lock currently has the following distinct uses: ... - Threads lifetime cycle, in particular, counting of the threads in the process, and interlocking with process mutex and thread lock. The main reason of this is that turnstile locks are after thread locks, so you e.g. cannot unlock blockable mutex (think process mutex) while owning thread lock. - Virtual and profiling itimers, since the timers activation is done from the clock interrupt context. Replace the p_slock by p_itimmtx and PROC_ITIMLOCK(). - Profiling code (profil(2)), for similar reason. Replace the p_slock by p_profmtx and PROC_PROFLOCK(). - Resource usage accounting. Need for the spinlock there is subtle, my understanding is that spinlock blocks context switching for the current thread, which prevents td_runtime and similar fields from changing (updates are done at the mi_switch()). Replace the p_slock by p_statmtx and PROC_STATLOCK(). The split is done mostly for code clarity, and should not affect scalability. Tested by: pho Sponsored by: The FreeBSD Foundation MFC after: 1 week		2014-11-26 14:10:00 +00:00
..
freebsd32	Remove the no-at variants of the kern_xx() syscall helpers. E.g., we	2014-11-13 18:01:51 +00:00
ia32	Improve support for XSAVE with debuggers.	2014-11-21 20:53:17 +00:00
linprocfs	Fix build on 32-bit machines.	2014-09-18 20:29:17 +00:00
linsysfs	Provide includes that are needed in these files, and before were read	2013-10-26 18:18:50 +00:00
linux	The process spin lock currently has the following distinct uses:	2014-11-26 14:10:00 +00:00
ndis	Fix multiple incorrect SYSCTL arguments in the kernel:	2014-10-21 07:31:21 +00:00
netbsd
svr4	The process spin lock currently has the following distinct uses:	2014-11-26 14:10:00 +00:00
x86bios	Pull in r267961 and r267973 again. Fix for issues reported will follow.	2014-06-28 03:56:17 +00:00