vmm(4): emulate PKRU XSAVE area and features.
vmm(4) has supported guests using memory protection keys based on
OpenBSD's implementation on Intel amd64 devices. Recent releases
of Linux distros use kernel builds expecting to save and restore
the PKRU state using XSAVE/XRSTOR. This leads to Linux guests
panicking on boot as they expect to see certain CPUID features.
This change adds support to the CPUID emulation to describe the
proper size and offset required for PKRU state so a guest can choose
to use XSAVE/XRSTOR to handle PKRU on context switches.
This does not change how the OpenBSD host uses XSAVE/XRSTOR. vmm(4)
continues to directly save and restore PKRU using WRPKRU/RDPKRU
instructions on guest entry and exit.
ok mlarkin@
gcc/15 builds on sparc64 following claudio's ld.so fix
gcc/15 stays unhooked anyway. Also drop BROKEN-sparc64 from gcc/11
which failed for the same reason.
Increase the size of the unhibernate chunk table
The unhibernate chunk table was previously capable of managing machines up
to approximately 102GB RAM. On machines with more memory than this,
unhibernate failed. This doubles the size of the chunktable to account
for larger RAM sizes.
ok krw, deraadt
remove unused and outdated devel/ruby-rgen
MAINTAINER dropped it in 2019, we package 0.8.2 from 2016 and upstream
is active with 0.10.2 from earlier this year.
sysutils/ruby-puppet used to use it long ago.
No screams on port@ after a week.
OK jeremy