From: Michal Hocko <mhocko@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Tony Luck <tony.luck@intel.com>,
linux-ia64@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>,
Pingfan Liu <kernelfans@gmail.com>,
linux-mm@kvack.org, Ingo Molnar <mingo@elte.hu>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v3 2/2] mm: be more verbose about zonelist initialization
Date: Wed, 13 Feb 2019 17:18:32 +0100 [thread overview]
Message-ID: <20190213161832.GT4525@dhcp22.suse.cz> (raw)
In-Reply-To: <1433a7e9-87b2-7e8d-a87d-dcffe486635c@intel.com>
On Wed 13-02-19 08:14:50, Dave Hansen wrote:
> On 2/13/19 1:43 AM, Michal Hocko wrote:
> >
> > We have seen several bugs where zonelists have not been initialized
> > properly and it is not really straightforward to track those bugs down.
> > One way to help a bit at least is to dump zonelists of each node when
> > they are (re)initialized.
>
> Were you thinking of boot-time bugs and crashes, or just stuff going
> wonky after boot?
Mostly boot time. I haven't seen hotplug related bugs in this direction.
All the issues I have seen so far is that we forget a node altogether
and it ends up with no zonelists at all. But who knows maybe we have
some hidden bugs where zonelists is initialized only partially for some
reason and there is no real way to find out.
> We don't have the zonelists dumped in /proc anywhere, do we? Would that
> help?
I would prefer to not export such an implementation detail into proc
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-02-13 16:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 9:53 [PATCH 0/2] x86, numa: always initialize all possible nodes Michal Hocko
2019-02-12 9:53 ` [PATCH 1/2] " Michal Hocko
2019-05-01 19:12 ` Barret Rhoden
2019-05-02 13:00 ` Michal Hocko
2019-06-26 13:54 ` Michal Hocko
2019-02-12 9:53 ` [PATCH 2/2] mm: be more verbose about zonelist initialization Michal Hocko
2019-02-13 0:12 ` kbuild test robot
2019-02-13 2:13 ` kbuild test robot
2019-02-13 9:40 ` [PATCH v2 " Michal Hocko
2019-02-13 9:43 ` [PATCH v3 " Michal Hocko
2019-02-13 10:32 ` Peter Zijlstra
2019-02-13 11:50 ` Michal Hocko
2019-02-13 13:11 ` Peter Zijlstra
2019-02-13 13:41 ` Michal Hocko
2019-02-13 16:14 ` Dave Hansen
2019-02-13 16:18 ` Michal Hocko [this message]
2019-02-12 10:19 ` [PATCH 0/2] x86, numa: always initialize all possible nodes Mike Rapoport
2019-02-26 13:12 ` Michal Hocko
2019-04-15 11:42 ` Michal Hocko
2019-04-15 15:43 ` Dave Hansen
2019-04-16 6:54 ` 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=20190213161832.GT4525@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=dave.hansen@intel.com \
--cc=kernelfans@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tony.luck@intel.com \
--cc=x86@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).