From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: dan.j.williams@intel.com, vishal.l.verma@intel.com, jmoyer@redhat.com
Cc: linux-nvdimm@lists.01.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [PATCH v4 0/6] Validating namespace size and start address attributes.
Date: Mon, 20 Jan 2020 19:37:43 +0530 [thread overview]
Message-ID: <20200120140749.69549-1-aneesh.kumar@linux.ibm.com> (raw)
When creating a new namespace, the kernel needs to make sure namespace size and
start address are correctly aligned to SUBSECTION_SIZE. This ensures kernel can
enable/disable namespace without conflicting with memory hotplug rules. Without this,
a namespace that partially covers a SUBSECTION can prevent the creation of an
adjacent namespace because the hotplug subsystem will find the subsection already active.
To make sure new kernel don't break an existing install with an unaligned start/size attribute,
while initializing the namespace the kernel validates these attribute against direct-map
mapping page size rather than subsection size.
Aneesh Kumar K.V (6):
libnvdimm/namespace: Make namespace size validation arch dependent
libnvdimm/namespace: Validate namespace start addr and size
libnvdimm/namespace: Add arch dependent callback for namespace create
time validation
libnvdimm/namespace: Validate namespace size when creating a new
namespace.
libnvdimm/namespace: Align DPA based on arch restrictions
libnvdimm/namespace: Expose arch specific supported size align value
arch/arm64/mm/flush.c | 13 +++++
arch/powerpc/lib/pmem.c | 20 ++++++++
arch/x86/mm/pageattr.c | 13 +++++
drivers/nvdimm/namespace_devs.c | 85 +++++++++++++++++++++++++++++++--
include/linux/libnvdimm.h | 2 +
5 files changed, 128 insertions(+), 5 deletions(-)
--
2.24.1
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org
next reply other threads:[~2020-01-20 14:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 14:07 Aneesh Kumar K.V [this message]
2020-01-20 14:07 ` [PATCH v4 1/6] libnvdimm/namespace: Make namespace size validation arch dependent Aneesh Kumar K.V
2020-01-24 5:57 ` Dan Williams
2020-01-24 7:34 ` Aneesh Kumar K.V
2020-01-24 16:45 ` Dan Williams
2020-01-24 17:07 ` Aneesh Kumar K.V
2020-01-24 18:25 ` Dan Williams
2020-01-26 11:41 ` Aneesh Kumar K.V
2020-01-24 17:08 ` Aneesh Kumar K.V
2020-01-20 14:07 ` [PATCH v4 2/6] libnvdimm/namespace: Validate namespace start addr and size Aneesh Kumar K.V
2020-01-25 1:55 ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 3/6] libnvdimm/namespace: Add arch dependent callback for namespace create time validation Aneesh Kumar K.V
2020-01-25 1:59 ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 4/6] libnvdimm/namespace: Validate namespace size when creating a new namespace Aneesh Kumar K.V
2020-01-25 2:22 ` Dan Williams
2020-01-20 14:07 ` [PATCH v4 5/6] libnvdimm/namespace: Align DPA based on arch restrictions Aneesh Kumar K.V
2020-01-20 14:07 ` [PATCH v4 6/6] libnvdimm/namespace: Expose arch specific supported size align value Aneesh Kumar K.V
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=20200120140749.69549-1-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=dan.j.williams@intel.com \
--cc=jmoyer@redhat.com \
--cc=linux-nvdimm@lists.01.org \
--cc=vishal.l.verma@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).