From: "Jérôme Glisse" <jglisse@redhat.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Cc: "John Hubbard" <jhubbard@nvidia.com>,
"Dan Williams" <dan.j.williams@intel.com>,
"Naoya Horiguchi" <n-horiguchi@ah.jp.nec.com>,
"David Nellans" <dnellans@nvidia.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Ross Zwisler" <ross.zwisler@linux.intel.com>
Subject: [HMM 02/15] mm/put_page: move ZONE_DEVICE page reference decrement v2
Date: Fri, 21 Apr 2017 23:30:24 -0400 [thread overview]
Message-ID: <20170422033037.3028-3-jglisse@redhat.com> (raw)
In-Reply-To: <20170422033037.3028-1-jglisse@redhat.com>
Move page reference decrement of ZONE_DEVICE from put_page()
to put_zone_device_page() this does not affect non ZONE_DEVICE
page.
Doing this allow to catch when a ZONE_DEVICE page refcount reach
1 which means the device is no longer reference by any one (unlike
page from other zone, ZONE_DEVICE page refcount never reach 0).
This patch is just a preparatory patch for HMM.
Changes since v1:
- commit message
Signed-off-by: JA(C)rA'me Glisse <jglisse@redhat.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Ross Zwisler <ross.zwisler@linux.intel.com>
---
include/linux/mm.h | 14 +++++++++++---
kernel/memremap.c | 6 ++++++
2 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index c82e8db..022423c 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -821,11 +821,19 @@ static inline void put_page(struct page *page)
{
page = compound_head(page);
+ /*
+ * ZONE_DEVICE pages should never have their refcount reach 0 (this
+ * would be a bug), so call page_ref_dec() in put_zone_device_page()
+ * to decrement page refcount and skip __put_page() here, as this
+ * would worsen things if a ZONE_DEVICE had a refcount bug.
+ */
+ if (unlikely(is_zone_device_page(page))) {
+ put_zone_device_page(page);
+ return;
+ }
+
if (put_page_testzero(page))
__put_page(page);
-
- if (unlikely(is_zone_device_page(page)))
- put_zone_device_page(page);
}
#if defined(CONFIG_SPARSEMEM) && !defined(CONFIG_SPARSEMEM_VMEMMAP)
diff --git a/kernel/memremap.c b/kernel/memremap.c
index ea714ee..97ef676 100644
--- a/kernel/memremap.c
+++ b/kernel/memremap.c
@@ -190,6 +190,12 @@ EXPORT_SYMBOL(get_zone_device_page);
void put_zone_device_page(struct page *page)
{
+ /*
+ * ZONE_DEVICE page refcount should never reach 0 and never be freed
+ * to kernel memory allocator.
+ */
+ page_ref_dec(page);
+
put_dev_pagemap(page->pgmap);
}
EXPORT_SYMBOL(put_zone_device_page);
--
2.9.3
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-22 3:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 3:30 [HMM 00/15] HMM (Heterogeneous Memory Management) v20 Jérôme Glisse
2017-04-22 3:30 ` [HMM 01/15] mm, memory_hotplug: introduce add_pages Jérôme Glisse
2017-04-22 3:30 ` Jérôme Glisse [this message]
2017-04-22 4:46 ` [HMM 02/15] mm/put_page: move ZONE_DEVICE page reference decrement v2 Dan Williams
2017-04-22 3:30 ` [HMM 03/15] mm/unaddressable-memory: new type of ZONE_DEVICE for unaddressable memory Jérôme Glisse
2017-04-22 5:30 ` Dan Williams
2017-04-22 18:11 ` Jerome Glisse
2017-04-23 13:13 ` Dan Williams
2017-04-24 0:39 ` John Hubbard
2017-04-25 7:08 ` Jon Masters
2017-04-22 3:30 ` [HMM 04/15] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY Jérôme Glisse
2017-04-22 3:30 ` [HMM 05/15] mm/migrate: new memory migration helper for use with device memory v4 Jérôme Glisse
2017-04-22 3:30 ` [HMM 06/15] mm/migrate: migrate_vma() unmap page from vma while collecting pages Jérôme Glisse
2017-04-22 3:30 ` [HMM 07/15] mm/hmm: heterogeneous memory management (HMM for short) v2 Jérôme Glisse
2017-04-22 3:30 ` [HMM 08/15] mm/hmm/mirror: mirror process address space on device with HMM helpers v2 Jérôme Glisse
2017-04-22 3:30 ` [HMM 09/15] mm/hmm/mirror: helper to snapshot CPU page table v2 Jérôme Glisse
2017-04-22 3:30 ` [HMM 10/15] mm/hmm/mirror: device page fault handler Jérôme Glisse
2017-04-22 3:30 ` [HMM 11/15] mm/migrate: support un-addressable ZONE_DEVICE page in migration Jérôme Glisse
2017-04-22 3:30 ` [HMM 12/15] mm/migrate: allow migrate_vma() to alloc new page on empty entry v2 Jérôme Glisse
2017-04-22 3:30 ` [HMM 13/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v3 Jérôme Glisse
2017-04-22 3:30 ` [HMM 14/15] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v3 Jérôme Glisse
2017-04-22 3:30 ` [HMM 15/15] hmm: heterogeneous memory management documentation Jérôme Glisse
-- strict thread matches above, loose matches on Subject: below --
2017-04-24 18:12 [HMM 00/15] HMM (Heterogeneous Memory Management) v21 Jérôme Glisse
2017-04-24 18:12 ` [HMM 02/15] mm/put_page: move ZONE_DEVICE page reference decrement v2 Jérôme Glisse
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=20170422033037.3028-3-jglisse@redhat.com \
--to=jglisse@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dnellans@nvidia.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=ross.zwisler@linux.intel.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;
as well as URLs for NNTP newsgroup(s).