[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1433a7e9-87b2-7e8d-a87d-dcffe486635c@intel.com>
Date: Wed, 13 Feb 2019 08:14:50 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Michal Hocko <mhocko@...nel.org>, linux-mm@...ck.org
Cc: Pingfan Liu <kernelfans@...il.com>,
Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Michael Ellerman <mpe@...erman.id.au>,
Tony Luck <tony.luck@...el.com>, linuxppc-dev@...ts.ozlabs.org,
linux-ia64@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...e.hu>, Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH v3 2/2] mm: be more verbose about zonelist initialization
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?
We don't have the zonelists dumped in /proc anywhere, do we? Would that
help?
Powered by blists - more mailing lists