Page MenuHomeFreeBSD

x86/xen: stop assuming kernel memory loading order in PVH
ClosedPublic

Authored by royger on Jun 28 2022, 3:53 PM.
Tags
None
Referenced Files
F154763330: D35628.id107579.diff
Wed, Apr 29, 9:40 AM
F154761162: D35628.id107579.diff
Wed, Apr 29, 9:33 AM
Unknown Object (File)
Tue, Apr 28, 10:58 PM
Unknown Object (File)
Tue, Apr 28, 5:29 PM
Unknown Object (File)
Tue, Apr 28, 5:25 PM
Unknown Object (File)
Tue, Apr 28, 4:15 PM
Unknown Object (File)
Tue, Apr 28, 11:59 AM
Unknown Object (File)
Tue, Apr 28, 9:11 AM
Subscribers

Details

Summary

Do not assume that start_info will always be loaded at the highest
memory address, and instead check the position of all the loaded
elements in order to find the last loaded one, and thus a likely safe
place to use as early boot allocation memory space.

Reported by: markj, cpercival
Sponsored by: Citrix Systems R&D

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 46179
Build 43068: arc lint + arc unit

Event Timeline

sys/x86/xen/pv.c
154

max() is not really appropriate here. It only compares a pair of unsigned ints. (Yes, it's too confusing.) The MAX() macro is a better alternative. I think this happens to work because the addresses involved are small, but it'd still be better to switch away from its use.

176

Extra newline.

royger added inline comments.
sys/x86/xen/pv.c
154

Yes, all addresses should be below 4G, and hence fit in an unsigned int. That mess with max() is confusing, will switch to MAX() instead.

  • Use MAX() instead of max().
  • Remove extra newline.
This revision is now accepted and ready to land.Jun 29 2022, 3:04 PM