Page MenuHomeFreeBSD

Make vm_map_max/min/pmap KBI stable.
ClosedPublic

Authored by kib on Mar 29 2018, 8:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jan 17, 10:05 AM
Unknown Object (File)
Dec 10 2024, 5:45 AM
Unknown Object (File)
Nov 30 2024, 9:05 PM
Unknown Object (File)
Nov 26 2024, 9:13 PM
Unknown Object (File)
Nov 26 2024, 12:49 AM
Unknown Object (File)
Oct 4 2024, 1:57 PM
Unknown Object (File)
Oct 4 2024, 11:48 AM
Unknown Object (File)
Oct 1 2024, 5:28 PM
Subscribers

Details

Summary

There are out of tree consumers of vm_map_min() and vm_map_max(), and I believe there are consumers of vm_map_pmap(), although the later is arguably less in the need of KBI-stable interface. For the consumers benefit, make modules using this KPI not depended on the struct vm_map layout.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

markj added inline comments.
sys/vm/vm_map.c
4322 ↗(On Diff #40900)

Shouldn't these routines just call the corresponding inline function?

This revision is now accepted and ready to land.Mar 29 2018, 8:28 PM
sys/vm/vm_map.c
4322 ↗(On Diff #40900)

I considered it and my feel was that it would only add an additional layer of obfuscation. I belive we did not make vm_page_*_KBI functions calling non-KBI variants for the same reason.

sys/vm/vm_map.c
4322 ↗(On Diff #40900)

Ok, fair enough.

This revision was automatically updated to reflect the committed changes.