bump MAXDSIZ to 128G on amd64 and 64G on arm64
discussed with kettenis@, ok deraadt@

Aggressively randomize the location of the stack on all 64-bit architectures
except alpha. This will put the stack at a random location in the upper
1/4th of the userland virtual address space provi

Aggressively randomize the location of the stack on all 64-bit architectures
except alpha. This will put the stack at a random location in the upper
1/4th of the userland virtual address space providing up to 26 additional
bits of randomness in the address. Skip alpha for now since it currently
puts the stack at a (for a 64-bit architecture) very low address. Skip
32-bit architectures for now as well since those have a much smaller
virtual address space and we need more time to figure out what a safe
amount of extra randomizations is. These architectures will continue to
use a mildly randomized stack address through the existing stackgap random
mechanism. We will revisit this after 7.3 is released.

This should make it harder for an attacker to find the stack.

ok deraadt@, miod@

show more ...

Bump VM_MAX_KERNEL_ADDRESS so that we have about 16G of KVA. Since
we need KVA to keep track of all the RAM pages, machines with a lot
of memory easily exhaust our KVA space. We need about 1G of KV

Bump VM_MAX_KERNEL_ADDRESS so that we have about 16G of KVA. Since
we need KVA to keep track of all the RAM pages, machines with a lot
of memory easily exhaust our KVA space. We need about 1G of KVA
per 32G of memory, so with 16G of KVA we can maintain close to 512G
of memory.

ok kettenis@

show more ...

We actually support 39-bit VA's in userland.

ok patrick@, jsg@

Implement pmap_growkernel(). Bump VM_MAX_KERNEL_ADDRESS now that we no
longer pre-allocate the complete kernel page tables.

ok patrick@, visa@

set MAXSSIZ to the same value as on all other architectures (32MB)
ok deraadt@

remove duplicated PAGE macros and drop type suffix
ok kettenis@

Use EFI memory map to discover available physical memory.
Fall back on improved code that parses the FDT /memory node.
However, on machines with "real" UEFI firmware, /memory may include
reserved mem

Use EFI memory map to discover available physical memory.
Fall back on improved code that parses the FDT /memory node.
However, on machines with "real" UEFI firmware, /memory may include
reserved memory that we shouldn't use (it does on the Overdrive 1000).
On those machines, make sure that you use BOOTAA64 0.3 or later such that
the EFI memory map gets used.

For now, print out the EFI memory map to help debug any issues.

ok patrick@

show more ...

Import of OpenBSD/arm64

This commit contains all the kernel files related to the OpenBSD/arm64
port. It is based on the PowerPC pmap, loongson, arm/armv7 code and
FreeBSD aarch64 code. Hard work d

Import of OpenBSD/arm64

This commit contains all the kernel files related to the OpenBSD/arm64
port. It is based on the PowerPC pmap, loongson, arm/armv7 code and
FreeBSD aarch64 code. Hard work done by Dale Rahn.

show more ...