From: David Hildenbrand <david@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Michal Hocko <mhocko@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Pavel Tatashin <pasha.tatashin@oracle.com>
Subject: [PATCH v1 0/2] mm/page_alloc: memmap_init_zone() cleanups
Date: Mon, 13 Jan 2020 15:40:33 +0100 [thread overview]
Message-ID: <20200113144035.10848-1-david@redhat.com> (raw)
Two cleanups for "[PATCH] mm/page_alloc: Skip non present sections on zone
initialization" [1], whereby one cleanup seems to also be a fix for a
(theoretial?) kernelcore=mirror case - unless I am messing something up :)
[1] https://lkml.kernel.org/r/20191230093828.24613-1-kirill.shutemov@linux.intel.com
David Hildenbrand (2):
mm/page_alloc: fix and rework pfn handling in memmap_init_zone()
mm: factor out next_present_section_nr()
include/linux/mmzone.h | 10 ++++++++++
mm/page_alloc.c | 20 ++++++++------------
mm/sparse.c | 10 ----------
3 files changed, 18 insertions(+), 22 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-13 14:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 14:40 David Hildenbrand [this message]
2020-01-13 14:40 ` [PATCH v1 1/2] mm/page_alloc: fix and rework pfn handling in memmap_init_zone() David Hildenbrand
2020-02-03 21:35 ` Alexander Duyck
2020-02-03 21:44 ` David Hildenbrand
2020-02-03 23:17 ` Alexander Duyck
2020-02-04 8:40 ` David Hildenbrand
2020-01-13 14:40 ` [PATCH v1 2/2] mm: factor out next_present_section_nr() David Hildenbrand
2020-01-13 22:41 ` Kirill A. Shutemov
2020-01-13 22:57 ` David Hildenbrand
2020-01-13 23:02 ` David Hildenbrand
2020-01-14 10:41 ` Kirill A. Shutemov
2020-01-14 10:49 ` David Hildenbrand
2020-01-14 15:52 ` Kirill A. Shutemov
2020-01-14 16:50 ` David Hildenbrand
2020-01-14 16:52 ` David Hildenbrand
2020-01-31 4:30 ` [PATCH v1 0/2] mm/page_alloc: memmap_init_zone() cleanups Andrew Morton
2020-02-03 14:49 ` Kirill A. Shutemov
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=20200113144035.10848-1-david@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@oracle.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