[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <56414993.8070709@labbott.name>
Date: Mon, 9 Nov 2015 17:34:11 -0800
From: Laura Abbott <laura@...bott.name>
To: Tony Luck <tony.luck@...il.com>,
Laura Abbott <labbott@...oraproject.org>
Cc: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Vlastimil Babka <vbabka@...e.cz>,
Bjorn Andersson <bjorn.andersson@...ymobile.com>,
Santosh Shilimkar <ssantosh@...nel.org>,
Russell King <rmk@....linux.org.uk>,
Kevin Hilman <khilman@...aro.org>,
Arnd Bergman <arnd@...db.de>,
Stephen Boyd <sboyd@...eaurora.org>,
Andy Gross <agross@...eaurora.org>,
Mel Gorman <mgorman@...e.de>,
Steven Rostedt <rostedt@...dmis.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCHv4] mm: Don't offset memmap for flatmem
On 11/9/15 3:20 PM, Tony Luck wrote:
>> @@ -4984,9 +4987,9 @@ static void __init_refok alloc_node_mem_map(struct pglist_data *pgdat)
>> */
>> if (pgdat == NODE_DATA(0)) {
>> mem_map = NODE_DATA(0)->node_mem_map;
>> -#ifdef CONFIG_HAVE_MEMBLOCK_NODE_MAP
>> +#if defined(CONFIG_HAVE_MEMBLOCK_NODE_MAP) || defined(CONFIG_FLATMEM)
>> if (page_to_pfn(mem_map) != pgdat->node_start_pfn)
>> - mem_map -= (pgdat->node_start_pfn - ARCH_PFN_OFFSET);
>> + mem_map -= offset;
>> #endif /* CONFIG_HAVE_MEMBLOCK_NODE_MAP */
>> }
>> #endif
>
> This piece breaks ia64. See the comment earlier in the function
> that "ia64 gets its own node_mem_map" ... so we skip the initialization
> of offset ... and arrive down here and just subtract "0" from mem_map.
>
> Attached patch fixes ia64 ... does ARM still work if this is applied?
>
> -Tony
>
Yes, this still fixes the problem for me. I see the pfn <-> page
translation working as expected.
Tested-by: Laura Abbott <laura@...bott.name>
Thanks,
Laura
--
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/
Powered by blists - more mailing lists