Keep top page on CloudABI to work around AMD Ryzen stability issues.
ClosedPublic
Actions

Authored by ed on Aug 1 2017, 6:28 PM.

Tags

None

Referenced Files

	F132324423: D11808.id31471.diff
	Wed, Oct 15, 10:03 PM

	F132324417: D11808.id31440.diff
	Wed, Oct 15, 10:03 PM

	F132324416: D11808.id.diff
	Wed, Oct 15, 10:03 PM

	F132280432: D11808.diff
	Wed, Oct 15, 11:40 AM

	Unknown Object (File)
	Fri, Sep 19, 10:36 AM

	Unknown Object (File)
	Sep 4 2025, 12:41 AM

	Unknown Object (File)
	Aug 16 2025, 7:42 PM

	Unknown Object (File)
	Aug 12 2025, 11:11 AM

View All Files

Subscribers

imp

Details

Reviewers

truckman
kib

Commits

rS321924: Keep top page on CloudABI to work around AMD Ryzen stability issues.

Summary

Similar to D11780, reduce sv_maxuser by one page inside of CloudABI.
This ensures that the stack, the vDSO and any allocations cannot touch
the top page of user virtual memory.

Considering that CloudABI userspace is completely oblivious to virtual
memory layout, don't bother making this conditional based on the CPU of
the running system.

Test Plan

C library unit tests still pass.