From: Wei Yang <richardw.yang@linux.intel.com>
To: akpm@linux-foundation.org, osalvador@suse.de, dan.j.williams@intel.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, bhe@redhat.com,
david@redhat.com, Wei Yang <richardw.yang@linux.intel.com>
Subject: [PATCH 0/3] Fixes "mm/sparsemem: support sub-section hotplug"
Date: Fri, 7 Feb 2020 07:16:26 +0800 [thread overview]
Message-ID: <20200206231629.14151-1-richardw.yang@linux.intel.com> (raw)
During reviewing David's code, I found current sub-section hotplug is
broken in several places.
The following link fix one potential issue, while David and I still spot
some suspicious points.
https://lkml.org/lkml/2020/2/6/334
The problem here is mainly about the memmap manipulation:
* memmap would be overwrite if not use SPARSEMEM_VMEMMAP
* only need to adjust memmap for SPARSEMEM_VMEMMAP
Wei Yang (3):
mm/sparsemem: adjust memmap only for SPARSEMEM_VMEMMAP
mm/sparsemem: get physical address to page struct instead of virtual
address to pfn
mm/sparsemem: avoid memmap overwrite for non-SPARSEMEM_VMEMMAP
mm/sparse.c | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
--
2.17.1
next reply other threads:[~2020-02-06 23:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 23:16 Wei Yang [this message]
2020-02-06 23:16 ` [PATCH 1/3] mm/sparsemem: adjust memmap only for SPARSEMEM_VMEMMAP Wei Yang
2020-02-07 2:00 ` Dan Williams
2020-02-07 11:06 ` Wei Yang
2020-02-06 23:16 ` [PATCH 2/3] mm/sparsemem: get physical address to page struct instead of virtual address to pfn Wei Yang
2020-02-07 2:19 ` Dan Williams
2020-02-07 3:10 ` Baoquan He
2020-02-07 3:21 ` Dan Williams
2020-02-07 3:36 ` Baoquan He
2020-02-07 4:05 ` Dan Williams
2020-02-07 11:13 ` Wei Yang
2020-02-07 12:14 ` Wei Yang
2020-02-07 16:44 ` Dan Williams
2020-02-07 10:51 ` Wei Yang
2020-02-07 11:26 ` Wei Yang
2020-02-09 13:50 ` Baoquan He
2020-02-09 14:14 ` David Hildenbrand
2020-02-10 0:36 ` Wei Yang
2020-02-07 4:11 ` Baoquan He
2020-02-07 10:53 ` Wei Yang
2020-02-06 23:16 ` [PATCH 3/3] mm/sparsemem: avoid memmap overwrite for non-SPARSEMEM_VMEMMAP Wei Yang
2020-02-07 2:06 ` Dan Williams
2020-02-07 3:50 ` Baoquan He
2020-02-07 11:02 ` Wei Yang
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=20200206231629.14151-1-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.