From: Michal Hocko <mhocko@kernel.org>
To: Pasha Tatashin <Pavel.Tatashin@microsoft.com>
Cc: "zaslonko@linux.ibm.com" <zaslonko@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"gerald.schaefer@de.ibm.com" <gerald.schaefer@de.ibm.com>
Subject: Re: [PATCH] memory_hotplug: fix the panic when memory end is not on the section boundary
Date: Mon, 10 Sep 2018 16:19:46 +0200 [thread overview]
Message-ID: <20180910141946.GJ10951@dhcp22.suse.cz> (raw)
In-Reply-To: <CAGM2reZuGAPmfO8x0TnHnqHci_Hsga3-CfM9+udJs=gUQCw-1g@mail.gmail.com>
On Mon 10-09-18 14:11:45, Pavel Tatashin wrote:
> Hi Michal,
>
> It is tricky, but probably can be done. Either change
> memmap_init_zone() or its caller to also cover the ends and starts of
> unaligned sections to initialize and reserve pages.
>
> The same thing would also need to be done in deferred_init_memmap() to
> cover the deferred init case.
Well, I am not sure TBH. I have to think about that much more. Maybe it
would be much more simple to make sure that we will never add incomplete
memblocks and simply refuse them during the discovery. At least for now.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-09-10 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 12:35 [PATCH] memory_hotplug: fix the panic when memory end is not on the section boundary Mikhail Zaslonko
2018-09-10 13:17 ` Michal Hocko
2018-09-10 13:46 ` Pasha Tatashin
2018-09-10 13:59 ` Michal Hocko
2018-09-10 14:11 ` Pasha Tatashin
2018-09-10 14:19 ` Michal Hocko [this message]
2018-09-10 14:32 ` Pasha Tatashin
2018-09-10 14:41 ` Michal Hocko
2018-09-10 15:26 ` Pasha Tatashin
2018-09-11 9:16 ` Michal Hocko
2018-09-12 14:28 ` Gerald Schaefer
2018-09-11 14:08 ` Zaslonko Mikhail
2018-09-11 14:06 ` Zaslonko Mikhail
2018-09-12 12:21 ` Michal Hocko
2018-09-12 13:03 ` Gerald Schaefer
2018-09-12 13:39 ` Michal Hocko
2018-09-12 14:27 ` Gerald Schaefer
2018-09-12 14:40 ` Pasha Tatashin
2018-09-12 15:51 ` Gerald Schaefer
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=20180910141946.GJ10951@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=Pavel.Tatashin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=gerald.schaefer@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=zaslonko@linux.ibm.com \
/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).