kernel: Simplify various redundant conditions.

Found-by: cppcheck

One was reported by dcb in <https://bugs.dragonflybsd.org/issues/3078>.

kernel - Incidental MPLOCK removal

* Remove misc #include <sys/mplock2.h> statements that are no longer needed.

* Replace mplock with acct_lock in kern_acct.c

* Replace mplock with msg_token in sy

kernel - Incidental MPLOCK removal

* Remove misc #include <sys/mplock2.h> statements that are no longer needed.

* Replace mplock with acct_lock in kern_acct.c

* Replace mplock with msg_token in sysv_msg.c

* Replace mplock with p->p_token in the profiling code.

show more ...

kernel/sysctl: Rename SYSCTL_ASSERT_XLOCKED -> SYSCTL_ASSERT_LOCKED.

6f1a15dc79a822710cc37e99f6a8bd9910e5e3f1 added shared locking and the
macro is intended to cover both cases, so use a better name.

sensors: By default, stick sensor tasks to the first cpu package

sensors: Accept -1 as sensor thread cpuid

The task will be register to the default sensor thread.

sensors: Create per-cpu sensor task threads

So that accessing to sensor device could be properly cpu localized,
e.g. accessing coretemp(4) could be localized to a proper cpu core,
and accessing ecc(

sensors: Create per-cpu sensor task threads

So that accessing to sensor device could be properly cpu localized,
e.g. accessing coretemp(4) could be localized to a proper cpu core,
and accessing ecc(4) could be localized to a proper cpu package.

show more ...

sensor: Stick sensors thread to the last CPU.

Round-robin CPU assignment could stick the sensors thread to CPU0,
which has many special tasks.

Submitted-by: YRabbit

sensor: Expose max id of sensor device through hw.sensors.dev_idmax

There could be so many sensor devices that MAXSENSORDEVICES is far
from enough, e.g. coretemp.

sensor: Fix sensor device numbering

Always use the lowest available sensor device number.

sensor: Fix sysctl tree creation

This allows:
- Attach sensor after installing sensor device.
- Detach sensor without de-installing sensor device.

sensor: Save OID of sensordev sysctl tree.

And allow sensordev sysctl tree registration to fail instead of panic,
e.g. upon duplicated sensordevs.

sensor: Use sysctl lock

Original devlist lock is not MPSAFE (it's locked find then unlocked
used). Since sensors are sysctl centric, we could just use sysctl
lock here.

sensor: sensor_task_schedule() should always be locked

sensor: Allocate task w/ M_WAITOK

And now sensor_task_register() will not fail.

sensor: Create task thread through SYSINIT

sensor: Function renaming and remove unnecessary comment.

sensor: Remove the NOSYSCTL8HACK ifndef test

NOSYSCTL8HACK is always not defined on DragonFly.

sensor: Staticize internal global variables

sensor: volatile is unnecessary for running

This fields are changed/checked w/ lock held.

sensors: Staticize internal functions

sensor: Utilize LOCK_INITIALIZER

The cmpset for lock initialization is _not_ safe (it requires at least
3 states and a spin loop, which is obviously an overkill when compared
w/ LOCK_INITIALIZER).

kernel/spinlock: Add a description to struct spinlock.

And add it to spin_init() and SPINLOCK_INITIALIZER().

Submitted-by: dclink (see <http://bugs.dragonflybsd.org/issues/2714>)
OK'd-by: dill

kernel/spinlock: Add a description to struct spinlock.

And add it to spin_init() and SPINLOCK_INITIALIZER().

Submitted-by: dclink (see <http://bugs.dragonflybsd.org/issues/2714>)
OK'd-by: dillon

show more ...

kernel - Change time_second to time_uptime for all expiration calculations

* Vet the entire kernel and change use cases for expiration calculations
using time_second to use time_uptime instead.

*

kernel - Change time_second to time_uptime for all expiration calculations

* Vet the entire kernel and change use cases for expiration calculations
using time_second to use time_uptime instead.

* Protects these expiration calculations from step changes in the wall time,
particularly needed for route table entries.

* Probably requires further variable type adjustments but the use of
time_uptime instead if time_second is highly unlikely to ever overrun
any demotions to int still present.

show more ...

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.

For kmalloc(), MALLOC() and contigmalloc(), use M_ZERO instead of
explicitly bzero()ing.

Reviewed-by: sephe