Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1349667 > unrolled thread
| Started by | Rob Herring <robh@kernel.org> |
|---|---|
| First post | 2016-03-04 00:00 +0100 |
| Last post | 2016-03-04 00:00 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH] of: alloc anywhere from memblock if range not specified Rob Herring <robh@kernel.org> - 2016-03-04 00:00 +0100
| From | Rob Herring <robh@kernel.org> |
|---|---|
| Date | 2016-03-04 00:00 +0100 |
| Subject | Re: [PATCH] of: alloc anywhere from memblock if range not specified |
| Message-ID | <r8KnT-5IL-7@gated-at.bofh.it> |
On Mon, Feb 22, 2016 at 07:15:44PM +0530, Vinayak Menon wrote: > early_init_dt_alloc_reserved_memory_arch passes end as 0 to > __memblock_alloc_base, when limits are not specified. But > __memblock_alloc_base takes end value of 0 as MEMBLOCK_ALLOC_ACCESSIBLE > and limits the end to memblock.current_limit. This results in regions > never being placed in HIGHMEM area, for e.g. CMA. > Let __memblock_alloc_base allocate from anywhere in memory if limits are > not specified. > > Acked-by: Marek Szyprowski <m.szyprowski@samsung.com> > Signed-off-by: Vinayak Menon <vinmenon@codeaurora.org> Applied and marked for stable. Rob
Back to top | Article view | linux.kernel
csiph-web