From: Christoph Lameter <cl@gentwo.de>
To: Dennis Zhou <dennis@kernel.org>
Cc: Alexey Makhalov <amakhalov@vmware.com>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"osalvador@suse.de" <osalvador@suse.de>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"tj@kernel.org" <tj@kernel.org>
Subject: Re: + mm-fix-panic-in-__alloc_pages.patch added to -mm tree
Date: Tue, 16 Nov 2021 13:30:45 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2111161329010.79746@gentwo.de> (raw)
In-Reply-To: <YZMq++inSmJegJmj@fedora>
On Mon, 15 Nov 2021, Dennis Zhou wrote:
> I need some clarification here. It sounds like memoryless nodes work on
> x86, but hotplug + memoryless nodes isn't a supported use case or you're
> introducing it as a new use case?
Could you do that step by step?
First add the new node and ensure everything is ok and that the memory is
online.
*After* that is done bring up the new processor and associate the
processor with *online* memory.
next prev parent reply other threads:[~2021-11-16 12:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211108205031.UxDPHBZWa%akpm@linux-foundation.org>
2021-11-09 8:37 ` + mm-fix-panic-in-__alloc_pages.patch added to -mm tree Michal Hocko
2021-11-09 8:42 ` David Hildenbrand
2021-11-09 11:00 ` Michal Hocko
2021-11-12 18:20 ` Dennis Zhou
2021-11-15 10:41 ` Michal Hocko
2021-11-15 11:04 ` Alexey Makhalov
2021-11-15 12:58 ` Michal Hocko
2021-11-15 23:11 ` Alexey Makhalov
2021-11-16 3:52 ` Dennis Zhou
2021-11-16 12:30 ` Christoph Lameter [this message]
2021-11-16 15:41 ` Michal Hocko
2021-12-14 10:11 ` Michal Hocko
2021-12-14 20:57 ` Andrew Morton
2021-12-15 10:05 ` Michal Hocko
2021-12-15 12:20 ` Michal Hocko
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=alpine.DEB.2.22.394.2111161329010.79746@gentwo.de \
--to=cl@gentwo.de \
--cc=akpm@linux-foundation.org \
--cc=amakhalov@vmware.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mm-commits@vger.kernel.org \
--cc=osalvador@suse.de \
--cc=stable@vger.kernel.org \
--cc=tj@kernel.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).