[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200130195258.6609880ac35f27f29238f804@linux-foundation.org>
Date: Thu, 30 Jan 2020 19:52:58 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Hildenbrand <david@...hat.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Alexey Dobriyan <adobriyan@...il.com>,
Bob Picco <bob.picco@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Dan Williams <dan.j.williams@...el.com>,
Michal Hocko <mhocko@...nel.org>,
Michal Hocko <mhocko@...e.com>,
Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
Oscar Salvador <osalvador@...e.de>,
Pavel Tatashin <pasha.tatashin@...cle.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Steven Sistare <steven.sistare@...cle.com>
Subject: Re: [PATCH v2 0/3] mm: fix max_pfn not falling on section boundary
On Wed, 11 Dec 2019 17:31:58 +0100 David Hildenbrand <david@...hat.com> wrote:
> Playing with different memory sizes for a x86-64 guest, I discovered that
> some memmaps (highest section if max_mem does not fall on the section
> boundary) are marked as being valid and online, but contain garbage. We
> have to properly initialize these memmaps.
>
> Looking at /proc/kpageflags and friends, I found some more issues,
> partially related to this.
We're still showing very little (ie no) review activity on this
patchset.
Powered by blists - more mailing lists