openbsd-src/sys/arch/ at master · jcs.org/openbsd-src

jcs.org / openbsd-src

jcs's openbsd hax

openbsd

openbsd-src / sys / arch /

at master 19 folders

Move annoying yet harmless diagnostic message into #ifdef DEBUG.

3 years ago

nable ngbe(4) on install media. Passes 'make release' build.

3 years ago

__syscall() is no longer neccessary since the system calls which needed it are now unpadded ok kettenis guenther

3 years ago

enable rkusbphy(4)

3 years ago

Enable mvtemp(4)

3 years ago

Delete obsolete /* ARGSUSED */ lint comments.

3 years ago

store bios version, needed for amdgpu Steam Deck quirk

3 years ago

sh, landisk: set HZ=64 again

3 years ago

Remove dangerous user-settable "addr" variable from MI boot loader, and only compile tty-related code (stty command, tty variable) on platforms where it makes sense for the boot loader to control it, rather than the PROM/firmware/whatever.

3 years ago

Add "machine poweroff" command on luna88k bootloader.

3 years ago

m88k also needs to define PMAP_CHECK_COPYIN as 1.

3 years ago

Delete obsolete /* ARGSUSED */ lint comments.

3 years ago

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.

3 years ago

timecounting: remove incomplete PPS support

3 years ago

Set the current pmap in macppc's pmap_activate

3 years ago

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.

3 years ago

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.

3 years ago

sh, landisk: set HZ=64 again

3 years ago

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.

3 years ago