tree 21cbafd87d1d9ea1d73989ab2970f5372b6d6e86
parent 8a584830721f09cc677f17cfa6c0a1de06cfacc3
author Nico Huber <nico.h@gmx.de> 1689378424 +0200
committer Martin L Roth <gaumless@gmail.com> 1693081777 +0000

memrange: Honor `limit` in the last step of top-down stealing

We only checked that the resource fits below the given `limit` in
memranges_find_entry(), but then accidentally placed it at the top
of the found memrange. As most resources have only a coarse limit,
e.g. the 4G barrier of 32-bit space, this became only visible when
artificially setting an unusual, lower limit on a resource.

So, for the final placement, use `MIN(limit, range end)` instead
of the range's end alone.

Change-Id: I3cc62ac3d427683c00ba0ac9f991fca62e99ce44
Signed-off-by: Nico Huber <nico.h@gmx.de>
Reviewed-on: https://review.coreboot.org/c/coreboot/+/76480
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Martin L Roth <gaumless@gmail.com>