linux-kernel - [RFC PATCH 0/2] allow bootmem to be freed to allocator late

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 23 Oct 2009 10:10:51 -0700
From:	Chris Wright <chrisw@...s-sol.org>
To:	linux-mm@...ck.org
Cc:	David Woodhouse <dwmw2@...radead.org>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH 0/2] allow bootmem to be freed to allocator late

Currently there is no way to release bootmem once the bootmem allocator
frees all unreserved memory.  This adds the ability to free reserved
pages directly to the page allocator after the bootmem allocator metadata
is already freed.  It's limited in scope since it's still all marked
__init, and creates a new entry point free_bootmem_late rather than
trying to do this automatically in free_bootmem.  Hence the RFC...

With this we are able to do something like allocate swiotlb, and then
free it later if we discover we had a hw iommu that doesn't need swiotlb.

 include/linux/bootmem.h |    1 +
 mm/bootmem.c            |   98 ++++++++++++++++++++++++++++++++++++----------
 2 files changed, 77 insertions(+), 22 deletions(-)

thanks,
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/