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
F166998499: D14902.diff
Tue, Aug 18, 11:54 AM
Unknown Object (File)
Sat, Aug 15, 7:59 AM
Unknown Object (File)
Tue, Aug 11, 12:41 PM
Unknown Object (File)
Tue, Aug 11, 12:36 AM
Unknown Object (File)
Mon, Aug 10, 10:17 AM
Unknown Object (File)
Mon, Aug 10, 10:00 AM
Unknown Object (File)
Sat, Aug 8, 10:44 PM
Unknown Object (File)
Tue, Jul 21, 6:08 AM
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

Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 15884

Event Timeline

markj added inline comments.
sys/vm/vm_map.c
4322

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

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

Ok, fair enough.

This revision was automatically updated to reflect the committed changes.