From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1755750AbdKGBPQ (ORCPT <rfc822;w@1wt.eu>);
        Mon, 6 Nov 2017 20:15:16 -0500
Received: from foss.arm.com ([217.140.101.70]:43260 "EHLO foss.arm.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S932584AbdKGBPM (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 6 Nov 2017 20:15:12 -0500
Date: Tue, 7 Nov 2017 01:15:17 +0000
From: Will Deacon <will.deacon@arm.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
        Sudeep Holla <sudeep.holla@arm.com>,
        "Kirill A. Shutemov" <kirill@shutemov.name>,
        Ingo Molnar <mingo@kernel.org>, Thomas Gleixner <tglx@linutronix.de>,
        Peter Zijlstra <peterz@infradead.org>, hpa@zytor.com,
        Andrew Morton <akpm@linux-foundation.org>, gorcunov@openvz.org,
        Andy Lutomirski <luto@amacapital.net>, bp@suse.de,
        open list <linux-kernel@vger.kernel.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [tip:x86/mm] mm/sparsemem: Allocate mem_section at runtime for
 CONFIG_SPARSEMEM_EXTREME=y
Message-ID: <20171107011516.GA13514@arm.com>
References: <20170929140821.37654-2-kirill.shutemov@linux.intel.com>
 <tip-83e3c48729d9ebb7af5a31a504f3fd6aff0348c4@git.kernel.org>
 <CAPKp9uZSFnzyzU647PajU6L6T38J--B+80FMW_0uwfhkxoveEA@mail.gmail.com>
 <20171102133433.hisnvz5iwmwdzjlz@node.shutemov.name>
 <44b8b5c8-0e9d-0534-0d0c-49618b292802@arm.com>
 <20171102141210.gu4cwpoq2e6o7liu@black.fi.intel.com>
 <CAOCOHw7L650+mGSc=+pmqHs1_NuF62FrHuyWq_DcOARh7J=gjA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOCOHw7L650+mGSc=+pmqHs1_NuF62FrHuyWq_DcOARh7J=gjA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Nov 06, 2017 at 11:00:09AM -0800, Bjorn Andersson wrote:
> On Thu, Nov 2, 2017 at 7:12 AM, Kirill A. Shutemov
> <kirill.shutemov@linux.intel.com> wrote:
> [..]
> > Could you try the patch below instead?
> >
> > From 4a9d843f9d939d958612b0079ebe5743f265e1e0 Mon Sep 17 00:00:00 2001
> > From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
> > Date: Thu, 2 Nov 2017 17:02:29 +0300
> > Subject: [PATCH] mm, sparse: Fix boot on arm64
> >
> > Since 83e3c48729d9 ("mm/sparsemem: Allocate mem_section at runtime for
> > CONFIG_SPARSEMEM_EXTREME=y") we allocate mem_section dynamically in
> > sparse_memory_present_with_active_regions(). But some architectures, like
> > arm64, don't use the routine to initialize sparsemem.
> >
> > Let's move the initialization into memory_present() it should cover all
> > architectures.
> >
> > Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> > Fixes: 83e3c48729d9 ("mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y")
> 
> Will you send out this patch, or will someone pick it up from here?
> 
> As with the other arm64 boards this is the difference between
> linux-next (and presumably v4.15-rc1) booting or not on my Qualcomm
> boards.
> 
> Tested-by: Bjorn Andersson <bjorn.andersson@linaro.org>

Yes, please can somebody get this into -next asap? I can't take it via
arm64, since this code isn't present there.

If you need it:

Acked-by: Will Deacon <will.deacon@arm.com>

Will