[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <147328716869.35069.16311932814998156819.stgit@dwillia2-desk3.amr.corp.intel.com>
Date: Wed, 07 Sep 2016 15:26:08 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: linux-nvdimm@...ts.01.org
Cc: Toshi Kani <toshi.kani@....com>,
Matthew Wilcox <mawilcox@...rosoft.com>,
David Airlie <airlied@...ux.ie>,
Nilesh Choudhury <nilesh.choudhury@...cle.com>,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
linux-mm@...ck.org, dri-devel@...ts.freedesktop.org,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
akpm@...ux-foundation.org,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Kai Zhang <kai.ka.zhang@...cle.com>
Subject: [PATCH v2 0/2] fix cache mode tracking for pmem + dax
While writing an improved changelog, as prompted by Andrew, for v1 of
"mm: fix cache mode of dax pmd mappings" [1], it struck me that
vmf_insert_pfn_pmd() is implemented correctly. Instead, it is the
memtype tree that is missing a memtype reservation for
devm_memremap_pages() ranges.
vmf_insert_pfn_pmd() is correct to validate the memtype before inserting
a mapping, but this highlights that vm_insert_mixed() is missing this
validation.
I would still like to take patch 1 through the nvdimm.git tree, with -mm
acks, along with the device-dax fixes for v4.8-rc6. Patch 2 can go the
typical -mm route for v4.9 since it has potential to change behavior in
its DRI usages, needs soak time in -next, and there no known memtype
conflict problems it would fix.
[1]: https://lists.01.org/pipermail/linux-nvdimm/2016-September/006781.html
---
Dan Williams (2):
mm: fix cache mode of dax pmd mappings
mm: fix cache mode tracking in vm_insert_mixed()
arch/x86/mm/pat.c | 17 ++++++++++-------
kernel/memremap.c | 9 +++++++++
mm/memory.c | 8 ++++++--
3 files changed, 25 insertions(+), 9 deletions(-)
Powered by blists - more mailing lists