r354570 dougm Nov. 9, 2019, 5:08 p.m.
consistency checking slows performance dramatically. This change
reduces the number of assertions checked by completely walking the
vm_map tree only when the write-lock is released, and only then if the
number of modifications to the tree since the last walk exceeds the
number of tree nodes.

Reviewed by: alc, kib
Tested by: pho
Differential Revision: https://reviews.freebsd.org/D22163
r354566 rmacklem Nov. 8, 2019, 11:58 p.m.
implemented by r354564.

This is a content change.
r354565 rmacklem Nov. 8, 2019, 11:49 p.m.
implemented by r354564.

This is a content change.
r354564 rmacklem Nov. 8, 2019, 11:39 p.m.
The current linux man page and testing done on a fairly recent linux5.n
kernel have identified two changes to the semantics of the linux
copy_file_range system call.
Since the copy_file_range(2) system call is intended to be linux compatible
and is only currently in head/current and not used by any commands,
it seems appropriate to update the system call to be compatible with
the current linux one.
The old linux man page stated that, if the
offset + len exceeded file_size for the input file, EINVAL should be returned.
Now, the semantics is to copy up to at most file_size bytes and return that
number of bytes copied. If the offset is at or beyond file_size, a return
of 0 bytes is done.
This patch modifies copy_file_range(2) to be linux compatible for this
semantic change.
A separate patch will change copy_file_range(2) for the other semantic
change, which allows the infd and outfd to refer to the same file, so
long as the byte ranges do not overlap.
r354563 kevans Nov. 8, 2019, 8:53 p.m.
Surgically pulling the patch from my debugging work lead to this slopiness-
my apologies.
r354562 markj Nov. 8, 2019, 8:47 p.m.
Submitted by:	rea
MFC with:	r354504
r354561 kevans Nov. 8, 2019, 8:14 p.m.
This was once set, but I removed it by the time I committed it because both
configurations use the same POWER_ID. This can be separated back out if the
situation changes.
r354560 kevans Nov. 8, 2019, 8:12 p.m.
DMA is currently disabled while I work out why it's broken, but this is
enough for upstream U-Boot + rpi-firmware + our rpi3-psci-monitor to boot
with the right config.

The RPi 4 is still not in a good "supported" state, as we have no
USB/PCI-E/Ethernet drivers, but if air-gapped pies only able to operate over
cereal is your thing, here's your guy.

Submitted by:	Robert Crowston (with modifications)
r354559 manu Nov. 8, 2019, 8:08 p.m.
In the EFI implementation in U-Boot no ConOut efi variable is created,
this cause loader to fallback to TERM_EMU implementation which is very
very very slow (and uses the ConOut device in the system table anyway).
The UEFI spec aren't clear as if this variable needs to exists or not.

Reviewed by:	imp, kevans
r354558 mmel Nov. 8, 2019, 7:29 p.m.
forgotten in r354556.

MFC after:	3 weeks
MFC with:	r354556
Noticed by:	manu
r354557 mmel Nov. 8, 2019, 7:15 p.m.
- add support for log2 based dividers
- use proper write mask when writing to divider register

MFC after:	3 weeks
Reviewed by:	manu
Differential Revision:  https://reviews.freebsd.org/D22283
r354556 mmel Nov. 8, 2019, 7:13 p.m.
- add support for fractional dividers
- allow to declare fixed and linked clock

MFC after:	3 weeks
Reviewed by:	manu
Differential Revision:  https://reviews.freebsd.org/D22282
r354555 mmel Nov. 8, 2019, 7:03 p.m.
- style
- unify dprinf defines
- make dprinf's 32-bit compatible
Not a functional change.

MFC after:	3 weeks
Reviewed by:	manu, imp
Differential Revision:  https://reviews.freebsd.org/D22281
r354554 mmel Nov. 8, 2019, 6:57 p.m.
This kind of clock nodes represent temporary placeholder for clocks
defined later in boot process. Also, these are necessary to break
circular dependencies occasionally occurring in complex clock graphs.

MFC after: 3 weeks
r354553 lwhsu Nov. 8, 2019, 6:56 p.m.
PR:		239380
Sponsored by:	The FreeBSD Foundation