Without this patch, the KASSERT(must_commit == 0,..) can be
triggered by the writeverf in the Direct I/O write reply changing.
This is not a situation that should cause a panic(). Correct
handling is to ignore the change in "writeverf" for Direct
I/O, since it is done with NFSWRITE_FILESYNC.

This patch modifies the semantics of the "must_commit"
argument slightly, allowing an initial value of 2 to indicate
that a change in "writeverf" should be ignored.
It also fixes the KASSERT()s.

This bug would affect few, since Direct I/O is not enabled
by default and "writeverf" rarely changes. Normally "writeverf"
only changes when a NFS server reboots, however I found the
bug when testing against a Linux 5.15.1 kernel nfsd, which
replied to a NFSWRITE_FILESYNC write with a "writeverf" of all
0x0 bytes.

MFC after:	2 weeks

Reading from Write Combining memory can be very-very slow. Try to use
shadow buffer to avoid such reads.

MFC after: 1 month
Differential Revision: https://reviews.freebsd.org/D33305

Suggested by:	 kib

MFC after:	3 days

Display of stats from a kernel core dump was never fully implemented.
Remove the dangling vars and remove the documentation.

MFC after:	3 days

MFC after:	3 days

MFC after:	3 days

MFC after:	3 days

MFC after:	3 days

MFC after:	3 days

Introduce new MSGBUF_WRAP flag, indicating that buffer has wrapped
at least once and does not keep zeroes from the last msgbuf_clear().
It allows msgbuf_peekbytes() to return only real data, not requiring
every consumer to trim the leading zeroes after doing pointless copy.
The most visible effect is that kern.msgbuf sysctl now always returns
proper zero-terminated string, not only after the first buffer wrap.

MFC after:	1 week
Sponsored by:	iXsystems, Inc.

MFC after:	3 days

MNTK_NOKNOTE was introduced in 679985d0
(dated 2005), VV_NOKNOTE in 34cc826a few
months later.

Neither was ever used by anything in the tree.

Correct bitmap operations in _kvm_bitmap_next.

Reviewed by:	jhb
MFC after:	2 weeks
Sponsored by:	The FreeBSD Foundation
Differential Revision:	https://reviews.freebsd.org/D19183

Now that MIPS isn't a recognized target for buildworld, move llvm mips
to off by default.

Sponsored by:		Netflix
Reviewed by:		dim
Differential Revision:	https://reviews.freebsd.org/D33364

As part of decommissioning mips support, remove the boot loader
support. Do this in advance of other boot loader work to limit the
amount of work that will be thrown away.

Sponsored by:		Netflix
Reviewed by:		jrtc27
Differential Revision:	https://reviews.freebsd.org/D33377

The elf loader needs to know how to reach into the gfx_fb code, so
simplify how we include files to find that stuff.

Sponsored by:		Netflix
Reviewed by:		manu, tsoome
Differential Revision:	https://reviews.freebsd.org/D33376

Reported by:	Taku YAMAMOTO
Sponsored by:	Netflix

Previosuly real time clock driver always set time format to 12-hour
mode. Fix this by choosing hour mode depending on HW register.

It's Word Wide Port Name, not World Word Port Name.

MFC after:	3 days

Sponsored by:	Innovate UK

Reviewed by:	manu, mmel
Sponsored by:	The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D33372

Sponsored by:	Rubicon Communications, LLC ("Netgate")

In pmap_ts_referenced we read the virtual address from pv->pv_va,
but then continue to use the pv struct to get the same value later
in the function.

Use the virtual address value we initially read rather than loading
from the pv struct each time.

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

Sponsored by:	Rubicon Communications, LLC ("Netgate")

MFC after:	1 week

MFC after:	1 week

MFC after:	2 weeks