linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>,
	linux-mm@kvack.org, "Dan Williams" <dan.j.williams@intel.com>
Subject: Re: [PATCH] mm, memory_hotplug: fix devm_memremap_pages() after memory_hotplug rework
Date: Thu, 6 Apr 2017 08:41:22 +0200	[thread overview]
Message-ID: <20170406064122.GA5497@dhcp22.suse.cz> (raw)
In-Reply-To: <12d241cc-b992-4576-c420-860bd5fd59d4@linux.vnet.ibm.com>

On Thu 06-04-17 11:04:20, Anshuman Khandual wrote:
> On 04/05/2017 04:19 PM, Michal Hocko wrote:
> > On Wed 05-04-17 16:05:23, Anshuman Khandual wrote:
> >> On 04/04/2017 10:21 PM, Jerome Glisse wrote:
> >>> Just a trivial fix.
> >>>
> >>> Signed-off-by: Jerome Glisse <jglisse@redhat.com>
> >>> Cc: Michal Hocko <mhocko@suse.com>
> >>> Cc: Dan Williams <dan.j.williams@intel.com>
> >>> ---
> >>>  kernel/memremap.c | 3 ++-
> >>>  1 file changed, 2 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/kernel/memremap.c b/kernel/memremap.c
> >>> index faa9276..bbbe646 100644
> >>> --- a/kernel/memremap.c
> >>> +++ b/kernel/memremap.c
> >>> @@ -366,7 +366,8 @@ void *devm_memremap_pages(struct device *dev, struct resource *res,
> >>>  	error = arch_add_memory(nid, align_start, align_size);
> >>>  	if (!error)
> >>>  		move_pfn_range_to_zone(&NODE_DATA(nid)->node_zones[ZONE_DEVICE],
> >>> -				align_start, align_size);
> >>> +					align_start >> PAGE_SHIFT,
> >>> +					align_size >> PAGE_SHIFT);
> >>
> >> All this while it was taking up addresses instead of PFNs ? Then
> >> how it was working correctly before ?
> > 
> > Because this code was embeded inside the arch_add_memory which did the
> > translation properly. See arch_add_memory implementations.
> 
> Got your point. Checked both mainline kernel and mmotm branch
> v4.11-rc5-mmotm-2017-04-04-15-00, in both the places the code
> snippet seems to be different than here. For example arch_add
> _memory has the following signature instead.
> 
> arch_add_memory(nid, align_start, align_size, true);
> 
> and I dont see move_pfn_range_to_zone() at all. Which tree/
> branch this patch is against ?

See http://lkml.kernel.org/r/20170330115454.32154-1-mhocko@kernel.org
this is a follow up fix for patch 5
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2017-04-06  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:51 [PATCH] mm, memory_hotplug: fix devm_memremap_pages() after memory_hotplug rework Jérôme Glisse
2017-04-04 16:57 ` Michal Hocko
2017-04-05 10:35 ` Anshuman Khandual
2017-04-05 10:49   ` Michal Hocko
2017-04-06  5:34     ` Anshuman Khandual
2017-04-06  6:41       ` Michal Hocko [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170406064122.GA5497@dhcp22.suse.cz \
    --to=mhocko@suse.com \
    --cc=dan.j.williams@intel.com \
    --cc=jglisse@redhat.com \
    --cc=khandual@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).