Nico Huber b2893e22e6 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>
2023-08-26 20:29:37 +00:00
..
2021-02-01 08:53:22 +00:00
2022-12-17 20:51:38 +00:00
2021-11-03 08:29:16 +00:00
2017-03-13 17:21:02 +01:00
2022-10-06 18:13:19 +00:00
2022-11-30 03:07:23 +00:00
2022-11-07 02:29:23 +00:00
2023-05-22 12:33:32 +00:00
2022-09-07 22:24:51 +00:00