Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp2645128ima; Mon, 22 Oct 2018 13:21:07 -0700 (PDT) X-Google-Smtp-Source: ACcGV63XcjQOfSSTu0z1hWMDJz+LKOsYu/u2tMTWk83Fnb+L+o++LdecOBmE24C/wntI+9h2jaR8 X-Received: by 2002:a62:2606:: with SMTP id m6-v6mr46732317pfm.104.1540239667933; Mon, 22 Oct 2018 13:21:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540239667; cv=none; d=google.com; s=arc-20160816; b=QCc91zDl0EAvJbhvy+WXd506wAM/bhiPP59lqprUag70cohqSVOJGoefTlN29jjxtI PpQB3I3u/iQp7Sz1NAxyJIjd8R1dua0lxn0NZz75MOk4lz+QcsWaWXwWXVDmtHwV9cdD j1oMUcnVIIYH9gcwSJEJMXe0WZHOA8asWFyD2UvqCyZ+lD30M6y8rZk+o+6q72gbomvF 2r1j+aMa8R6Apx/cLRpqUEPrgTqPnp0smQGlxK7DDQpE/U0lpb2QAYeBLma2GCsQGVA8 oijrZ2sVsoqBEOafriFqaxjiSPEP5ZwDSSN8R1+tu0ZN4zf7fCb5FQixVSKS0+OO9LeW y0nQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:in-reply-to:references:date :from:cc:to:subject; bh=sClhAVcJP/TIupWRfcVTdTIK5HemsoApwdW9D6IlpV4=; b=S4l/0ra17x8KTDdmA2QHl+nmc1HhvDG0Wy0l6gojvoz50q3Z2Bjuee2WA2EurBI+Cv 3luJx6k6ZHtjbFgn5NOZi+yTTE4b6tMePGRUursUyk46glCUwJEOB3rkAljOieT5Ux00 wS2G/68hxswZzIPJEA/SiURjoWjh1T0mCs4zj4RHKP+JygcYzQxc9J6+WJ67pKdyZZLL Opwu2LhEj9bNGrWMaX8c+TkwIwwIEnnRZzKJY3jyY+WeuN5zFC7iW9E9MEKil4yitw9H 7n2Q86DE2/LqG2aUu7f2b4vje2UdxRZbt9AflhCSuKdmoYEnjOxBT1TMQClAhIHIpFGB umUA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j6-v6si34723658pgb.62.2018.10.22.13.20.53; Mon, 22 Oct 2018 13:21:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729008AbeJWEit (ORCPT + 99 others); Tue, 23 Oct 2018 00:38:49 -0400 Received: from mga05.intel.com ([192.55.52.43]:13960 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725788AbeJWEir (ORCPT ); Tue, 23 Oct 2018 00:38:47 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Oct 2018 13:18:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,413,1534834800"; d="scan'208";a="101693469" Received: from viggo.jf.intel.com (HELO localhost.localdomain) ([10.54.77.144]) by orsmga001.jf.intel.com with ESMTP; 22 Oct 2018 13:18:48 -0700 Subject: [PATCH 8/9] dax/kmem: let walk_system_ram_range() search child resources To: linux-kernel@vger.kernel.org Cc: Dave Hansen , dan.j.williams@intel.com, dave.jiang@intel.com, zwisler@kernel.org, vishal.l.verma@intel.com, thomas.lendacky@amd.com, akpm@linux-foundation.org, mhocko@suse.com, linux-nvdimm@lists.01.org, linux-mm@kvack.org, ying.huang@intel.com, fengguang.wu@intel.com From: Dave Hansen Date: Mon, 22 Oct 2018 13:13:31 -0700 References: <20181022201317.8558C1D8@viggo.jf.intel.com> In-Reply-To: <20181022201317.8558C1D8@viggo.jf.intel.com> Message-Id: <20181022201331.8DDC3CDD@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org In the process of onlining memory, we use walk_system_ram_range() to find the actual RAM areas inside of the area being onlined. However, it currently only finds memory resources which are "top-level" iomem_resources. Children are not currently searched which causes it to skip System RAM in areas like this (in the format of /proc/iomem): a0000000-bfffffff : Persistent Memory (legacy) a0000000-afffffff : System RAM Changing the true->false here allows children to be searched as well. We need this because we add a new "System RAM" resource underneath the "persistent memory" resource when we use persistent memory in a volatile mode. Cc: Dan Williams Cc: Dave Jiang Cc: Ross Zwisler Cc: Vishal Verma Cc: Tom Lendacky Cc: Andrew Morton Cc: Michal Hocko Cc: linux-nvdimm@lists.01.org Cc: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org Cc: Huang Ying Cc: Fengguang Wu --- b/kernel/resource.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff -puN kernel/resource.c~mm-walk_system_ram_range-search-child-resources kernel/resource.c --- a/kernel/resource.c~mm-walk_system_ram_range-search-child-resources 2018-10-22 13:12:24.565930386 -0700 +++ b/kernel/resource.c 2018-10-22 13:12:24.572930386 -0700 @@ -445,6 +445,9 @@ int walk_mem_res(u64 start, u64 end, voi * This function calls the @func callback against all memory ranges of type * System RAM which are marked as IORESOURCE_SYSTEM_RAM and IORESOUCE_BUSY. * It is to be used only for System RAM. + * + * This will find System RAM ranges that are children of top-level resources + * in addition to top-level System RAM resources. */ int walk_system_ram_range(unsigned long start_pfn, unsigned long nr_pages, void *arg, int (*func)(unsigned long, unsigned long, void *)) @@ -460,7 +463,7 @@ int walk_system_ram_range(unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; while (start < end && !find_next_iomem_res(start, end, flags, IORES_DESC_NONE, - true, &res)) { + false, &res)) { pfn = (res.start + PAGE_SIZE - 1) >> PAGE_SHIFT; end_pfn = (res.end + 1) >> PAGE_SHIFT; if (end_pfn > pfn) _