src/sys/amd64, branch main

amd64: Remove a prototype for an unimplemented function

2026-07-21T22:46:42Z

Fixes: 6e93f5e4d693 ("amd64: FRED support") Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D58379

amd64: FRED support

2026-07-20T21:51:02Z

FRED support as defined starting from the SDM rev. 90, requires a new 'events' entry point to receive user and kernel mode exceptions and interrupts notifications from the hardware. A minimal asm trampoline is enough, rest can be implemented in C due to the clean FRED organization of the event reporting. The syscall entry is handled by a microptimized assembly path, directly calling into the amd64_syscall() handler, instead of the generic events entry point. Tested by: emaste Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D55829

vm: Make sure NULL is defined for vm_memattr_name()

2026-07-19T14:09:46Z

Fixes: a7e483ee146a ("vm_phys: Add a sysctl to dump registered fictitious memory ranges")

vm_phys: Add a sysctl to dump registered fictitious memory ranges

2026-07-19T00:29:40Z

I've wanted this a couple of times in the past. Save the memattr in the fictitious memory segment structure so that we can report it from the sysctl handler, and add conversion routines for each platform. Reviewed by: kib MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D58283

amd64 efirt: register all runtime regions as fictitious

2026-07-16T15:32:50Z

This is needed for VM_PHYS_TO_PAGE() to work, which is needed for pmap_map_io_transient() to work, which is needed for uiomove_fromphys() to work. PR: 296348 Reported and tested by: Anton Saietskii Reviewed by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D58274

MINIMAL: Add device md

2026-07-10T04:09:40Z

This can't be a loadable module, so add it to MINIMAL Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D58067

x86/local_apic.c: Add support for installing a thermal interrupt handler

2026-07-07T16:33:31Z

The thermal interrupt is initially masked. Thermal interrupt handling is enabled by calling lapic_enable_thermal(), which installs a (single) handler. [olce: Wrote the commit message.] Reviewed by: kib, olce MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D44454

sys: use curthread_pflags_set/restore to manage TDP_DEADLKTREAT for uio

2026-06-23T14:42:03Z

For i386, remove now unused label. Remove unneeded initialization of the 'save' local. Reviewed bu: brooks Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D57726

x86: Harmonize GENERIC and MINIMAL

2026-06-23T07:51:01Z

* Reorder MINIMAL so everything is in the same order as in GENERIC. * Wherever comments diverged, except for the explanatory comment at the top, copy the GENERIC version to MINIMAL. * Add KDTRACE_FRAME to i386 GENERIC; it was already in MINIMAL, and adding it to GENERIC seemed like the more correct move. With these changes, MINIMAL is a strict subset of GENERIC, apart from the identifier and the explanatory comment at the top. Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D57729

acpi: Forbid requesting S4 when S4BIOS is not supported

2026-06-22T13:50:03Z

Pending the OS-supported hibernate functionality, prevent requesting S4 when S4BIOS is not supported. To this end, make sure that acpi_supported_stypes[] indicates that POWER_STYPE_FW_HIBERNATE is not supported if 'acpi_s4bios_supported' is false, even if S4 is supported by the platform (which is only a power-down-like state, without any support to save the system image by itself). This will cause requests to enter S4, which are translated to POWER_STYPE_FW_HIBERNATE before reaching acpi_ReqSleepState()/acpi_EnterSleepState(), to fail in this case. Retire the 'hw.acpi.s4bios' sysctl knob, as having it to 0 by default (S4BIOS not supported) or setting it to 0 (default is 1 when S4BIOS is supported) could only lead, on a S4 request, to a power down without any possibility to restore the system (and, since a recent commit, it has not been possible anymore to force it to 1 when S4BIOS is not announced supported in the FACS table, which would cause a failure or a crash). When OS-supported hibernate is introduced, it will become the default hibernate method over S4BIOS, as we have not heard of any semi-recent hardware platform implementing it (and when it is, it usually needs a sufficiently large dedicated slice/partition, and does not use FreeBSD swap slices/partitions). Then, for people still wanting to use S4BIOS on older platforms that support it, the tentative plans are to modify acpiconf(8) to accept '4BIOS' as an argument to '-s', or modify zzz(8) so that one can pass a specific suspension method. Reviewed by: obiwac Event: Halifax Hackathon 202606 Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D57414