From: Boaz Harrosh <boaz@plexistor.com>
To: Ingo Molnar <mingo@redhat.com>,
Ross Zwisler <ross.zwisler@linux.intel.com>,
x86@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
"Roger C. Pao" <rcpao.enmotus@gmail.com>,
Dan Williams <dan.j.williams@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-nvdimm <linux-nvdimm@ml01.01.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Subject: [RFC 2/2] e820: Add the NvDIMM Memory type (type-12)
Date: Mon, 16 Feb 2015 13:16:43 +0200 [thread overview]
Message-ID: <54E1D19B.30405@plexistor.com> (raw)
In-Reply-To: <54E1CF5B.9020905@plexistor.com>
There are multiple vendors of DDR3 NvDIMMs out in the market today.
At various stages of development/production. It is estimated that
there are already more the 100ds of thousands chips sold to
testers and sites.
All the vendors I know of, tagged these chips as type-12 memory.
[THIS IS A CALL FOR ALL NvDIMM Vendors if you have used other
then type-12 NvDIMM, please email me and I will add support
for it]
Now the ACPI comity, as far as I know, did not yet define a
standard type for NvDIMM. Also, as far as I know any NvDIMM
standard will be defined for DDR4. So DDR3 NvDIMM will continue
to be supported by the individual vendors.
I Wish and call the ACPI comity to Define that NvDIMM is type-12.
Also for DDR4
In this patch I name type-12 "NvDIMM-12", but if there
are positive responses I would like to just name it "NvDIMM",
For any kind of DDR-X.
Actually is there any reason why I should not submit the final
version as "NvDIMM" from the get go. Then if the ACPI defines
another new type-Y Memory we can name both types "NvDIMM", No?
Please comment
Signed-off-by: Boaz Harrosh <boaz@plexistor.com>
---
arch/x86/include/uapi/asm/e820.h | 2 +-
arch/x86/kernel/e820.c | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/x86/include/uapi/asm/e820.h b/arch/x86/include/uapi/asm/e820.h
index d993e33..a0977e0 100644
--- a/arch/x86/include/uapi/asm/e820.h
+++ b/arch/x86/include/uapi/asm/e820.h
@@ -32,7 +32,7 @@
#define E820_ACPI 3
#define E820_NVS 4
#define E820_UNUSABLE 5
-
+#define E820_NvDIMM_12 12
/*
* reserved RAM used by kernel itself
diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
index 8cfd25f..17f7496 100644
--- a/arch/x86/kernel/e820.c
+++ b/arch/x86/kernel/e820.c
@@ -149,6 +149,9 @@ static void __init e820_print_type(u32 type)
case E820_UNUSABLE:
printk(KERN_CONT "unusable");
break;
+ case E820_NvDIMM_12:
+ printk(KERN_CONT "NvDIMM-12");
+ break;
default:
printk(KERN_CONT "type %u", type);
break;
@@ -908,6 +911,7 @@ static inline const char *e820_type_to_string(int e820_type)
case E820_NVS: return "ACPI Non-volatile Storage";
case E820_UNUSABLE: return "Unusable memory";
case E820_RESERVED: return "reserved";
+ case E820_NvDIMM_12: return "NvDIMM-12";
default: return "reserved-unkown";
}
}
@@ -922,6 +926,7 @@ static bool _is_reserved_type(int e820_type)
case E820_UNUSABLE:
return false;
case E820_RESERVED:
+ case E820_NvDIMM_12:
default:
return true;
}
--
1.9.3
next prev parent reply other threads:[~2015-02-16 11:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-16 11:07 [PATCH 0/2] e820: Fix handling of NvDIMM chips Boaz Harrosh
2015-02-16 11:13 ` [PATCH 1/2] e820: Don't let unknown DIMM type come out BUSY Boaz Harrosh
2015-02-16 11:16 ` Boaz Harrosh [this message]
2015-02-16 11:24 ` [PATCH 3/3] pmem: Allow request_mem to fail, (CONFIG_BLK_DEV_PMEM_IGNORE_REQUEST_MEM_RET) Boaz Harrosh
2015-02-17 20:52 ` Ross Zwisler
2015-02-18 9:58 ` Boaz Harrosh
2015-02-16 22:03 ` [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips Matthew Wilcox
2015-02-17 8:42 ` Boaz Harrosh
2015-02-18 18:15 ` Dan Williams
2015-02-18 18:30 ` Ingo Molnar
2015-02-18 18:44 ` Dan Williams
2015-02-18 18:53 ` Ingo Molnar
2015-02-18 19:18 ` Dan Williams
2015-02-18 19:27 ` Ingo Molnar
2015-02-18 19:35 ` Dan Williams
2015-02-19 10:27 ` Boaz Harrosh
2015-02-19 10:30 ` Ingo Molnar
2015-02-19 0:47 ` Christoph Hellwig
2015-02-19 1:03 ` Dan Williams
2015-02-19 10:01 ` Ingo Molnar
2015-02-19 10:29 ` Boaz Harrosh
2015-02-19 10:31 ` Ingo Molnar
2015-02-19 10:40 ` Boaz Harrosh
2015-02-19 9:25 ` Boaz Harrosh
2015-02-22 16:27 ` Christoph Hellwig
2015-02-22 17:05 ` Boaz Harrosh
2015-02-22 17:15 ` Boaz Harrosh
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=54E1D19B.30405@plexistor.com \
--to=boaz@plexistor.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=mingo@redhat.com \
--cc=rcpao.enmotus@gmail.com \
--cc=ross.zwisler@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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
Powered by JetHome