summaryrefslogtreecommitdiff
path: root/3rdparty
diff options
context:
space:
mode:
authorAaron Durbin <adurbin@chromium.org>2014-10-07 14:56:35 -0500
committerPatrick Georgi <pgeorgi@google.com>2015-03-21 08:44:57 +0100
commitb58f9e3a305e8bcef95f8c466f388746e7cbfb51 (patch)
tree1d77118df202858a903fdd66b3e76e1b6dbbb9a2 /3rdparty
parent29df70f0816fbe19731bcf9f061e142740b8e50a (diff)
downloadcoreboot-b58f9e3a305e8bcef95f8c466f388746e7cbfb51.tar.xz
cbmem: stop assuming 1MiB of memory can be mapped
The default mapping size is 1MiB of ram. However, not all systems allow 1MiB of memory to mapped depending on the kernel's memory map. Therefore, be explicit about the sizes to mmap(). The only path that wasn't cleaned up was the coverage path as that needs to handle dynamic cbmem. The correct way to fix that is to add a global like the timestamps that is set while parsing cbtable. BUG=chrome-os-partner:31355 BRANCH=None TEST=Can cbmem -ltc on ryu. Change-Id: I548afa5ddbe0a859f52bc2ab2d0931186ee378a5 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: df4991ce1da7f0c25e99d84222cbc8d3189d0d66 Original-Change-Id: I27b70ae8a8fba168d1c1829bbef0135c7b651eac Original-Signed-off-by: Aaron Durbin <adurbin@chromium.org> Original-Reviewed-on: https://chromium-review.googlesource.com/221971 Original-Reviewed-by: Furquan Shaikh <furquan@chromium.org> Original-Tested-by: Furquan Shaikh <furquan@chromium.org> Original-Commit-Queue: Furquan Shaikh <furquan@chromium.org> Reviewed-on: http://review.coreboot.org/8829 Tested-by: build bot (Jenkins) Reviewed-by: Stefan Reinauer <stefan.reinauer@coreboot.org>
Diffstat (limited to '3rdparty')
0 files changed, 0 insertions, 0 deletions