wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Substitute boolean_t/TRUE/FALSE by int/1/0.	mpi	2019-11-07	1	-4/+4
\|
*	Use the debugger mutex for `ddb_mp_mutex'. This should prevent a race	visa	2019-03-23	1	-16/+16
\| \| \| \| \| \| \| \| \| \|	that could leave `ddb_mp_mutex' locked if one CPU incremented `db_active' while another CPU was in the critical section. When the race hit, the debugger was unable to resume execution or switch between CPUs. Race analyzed by patrick@ OK mpi@ patrick@
*	Do not panic from ddb(4) when a lock requirement isn't fulfilled.	mpi	2018-03-20	1	-4/+1
\| \| \| \| \| \| \| \| \| \| \|	Extend the logic already present for panic() to any DDB-related operation such that if ddb(4) is entered because of a fault or other trap it is still possible to call 'boot reboot'. While here stop printing splassert() messages as well, to not fill the buffer. ok visa@, deraadt@
*	Rename Debugger() into db_enter().	mpi	2017-04-30	1	-3/+3
\| \| \| \| \| \| \|	Using a name with the 'db_' prefix makes it invisible from the dynamic profiler. ok deraadt@, kettenis@, visa@
*	DDB_REGS -> ddb_regs	mpi	2016-03-06	1	-5/+5
\|
*	One ddb interface is enough for ppc.	mpi	2016-03-05	1	-0/+339