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.
Details
Details
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 15884
Event Timeline
sys/vm/vm_map.c | ||
---|---|---|
4322 | Shouldn't these routines just call the corresponding inline function? |
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. |