Thread (3 messages) flat view 3 messages, 3 authors, 2018-07-12

Re: Boot failures with "mm/sparse: Remove CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER" on powerpc (was Re: mmotm 2018-07-10-16-50 uploaded)

From: Pavel Tatashin <hidden>
Date: 2018-07-12 15:09:20
Also in: linux-fsdevel, linux-mm, linux-next, lkml

Possibly related (same subject, not in this thread)

On Thu, Jul 12, 2018 at 5:50 AM Oscar Salvador
[off-list ref] wrote:
quoted
quoted
I just roughly check, but if I checked the right place,
vmemmap_populated() checks for the section to contain the flags we are
setting in sparse_init_one_section().
Yes.
quoted
But with this patch, we populate first everything, and then we call
sparse_init_one_section() in sparse_init().
As I said I could be mistaken because I just checked the surface.
Yes, this is right, sparse_init_one_section() is needed after every
populate call on ppc64. I am adding this to my sparse_init re-write,
and it actually simplifies code, as it avoids one extra loop, and
makes ppc64 to work.

Pavel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help