diff options
author | Stefan Brüns <stefan.bruens@rwth-aachen.de> | 2016-10-09 22:17:26 +0200 |
---|---|---|
committer | Alexander Graf <agraf@suse.de> | 2016-10-18 09:08:07 +0200 |
commit | 42417bc84d1d56f739d43d562773d4821cf1bf47 (patch) | |
tree | 52b540b625324c1f11b59d8f6a1803c1a0902fd1 /include/mvmfp.h | |
parent | ead1274b7f9578e346b3cdcb3d9e2002ef8f0e75 (diff) | |
download | u-boot-imx-42417bc84d1d56f739d43d562773d4821cf1bf47.zip u-boot-imx-42417bc84d1d56f739d43d562773d4821cf1bf47.tar.gz u-boot-imx-42417bc84d1d56f739d43d562773d4821cf1bf47.tar.bz2 |
efi_loader: Track size of pool allocations to allow freeing
We need a functional free_pool implementation, as otherwise each
allocate_pool causes growth of the memory descriptor table.
Different to free_pages, free_pool does not provide the size for the
to be freed allocation, thus we have to track the size ourselves.
As the only EFI requirement for pool allocation is an alignment of
8 bytes, we can keep allocating a range using the page allocator,
reserve the first 8 bytes for our bookkeeping and hand out the
remainder to the caller. This saves us from having to use any
independent data structures for tracking.
To simplify the conversion between pool allocations and the corresponding
page allocation, we create an auxiliary struct efi_pool_allocation.
Given the allocation size free_pool size can handoff freeing the page
range, which was indirectly allocated by a call to allocate_pool,
to free_pages.
Signed-off-by: Stefan Brüns <stefan.bruens@rwth-aachen.de>
Reviewed-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'include/mvmfp.h')
0 files changed, 0 insertions, 0 deletions