From patchwork Mon Feb 16 11:16:43 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Boaz Harrosh X-Patchwork-Id: 5832061 Return-Path: X-Original-To: patchwork-linux-nvdimm@patchwork.kernel.org Delivered-To: patchwork-parsemail@patchwork2.web.kernel.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.136]) by patchwork2.web.kernel.org (Postfix) with ESMTP id 84D3CBF440 for ; Mon, 16 Feb 2015 11:17:35 +0000 (UTC) Received: from mail.kernel.org (localhost [127.0.0.1]) by mail.kernel.org (Postfix) with ESMTP id A5B342011B for ; Mon, 16 Feb 2015 11:17:34 +0000 (UTC) Received: from ml01.01.org (ml01.01.org [198.145.21.10]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 5D98C200BE for ; Mon, 16 Feb 2015 11:17:33 +0000 (UTC) Received: from ml01.vlan14.01.org (localhost [IPv6:::1]) by ml01.01.org (Postfix) with ESMTP id 4F2C681261; Mon, 16 Feb 2015 03:17:33 -0800 (PST) X-Original-To: linux-nvdimm@lists.01.org Delivered-To: linux-nvdimm@lists.01.org Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3C8BE81261 for ; Mon, 16 Feb 2015 03:17:32 -0800 (PST) Received: by mail-wi0-f176.google.com with SMTP id h11so25237864wiw.3 for ; Mon, 16 Feb 2015 03:16:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vgf6iRGDmPFyrEGnE1jQsUBeBKbIZ8VpxUkzjRP8Rms=; b=C2VSY7VJ68QWu1VNDcJoW7CQNbZiYU4bGUkz4QtOuQUxcIxoJw9QilqbNGHOczoaPZ 8ZHcJIgSfk0TLIl/Xfhp5BUKVTxHkN+IGMw5WXCdd7s+6xmQJZWdc5IaARBYyTrh5t1M beQmX6K6DN5/ddtyBNCyIhUfZv5uaGwybFNypL5qR8uzd2evzusdVQ0/4Bt40al+g6ME rCCPxhlfmp3tWm2mrEyOVBCQT3YISo2y2oSjbmSzACShpWaTQDrIHnXvKLaSo3cWtJ3e y17PRik/08KXOsFFpU3Pd8Oej1d4qXWzbPoQNJY1DXjCsN+yAwJr3aTFlJfQEmpxeq2I 3hOA== X-Gm-Message-State: ALoCoQl7Id/tU8OSkvNSBhyFOB5pGDLH3NwZC18jo+PES+h3AwSr7OSRomHNZ8tW9YJ8GfbXJ/WG X-Received: by 10.194.200.68 with SMTP id jq4mr48476836wjc.128.1424085405816; Mon, 16 Feb 2015 03:16:45 -0800 (PST) Received: from [10.0.0.5] ([207.232.55.62]) by mx.google.com with ESMTPSA id u6sm17497558wix.12.2015.02.16.03.16.44 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Feb 2015 03:16:45 -0800 (PST) Message-ID: <54E1D19B.30405@plexistor.com> Date: Mon, 16 Feb 2015 13:16:43 +0200 From: Boaz Harrosh User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Ingo Molnar , Ross Zwisler , x86@kernel.org, linux-kernel , "Roger C. Pao" , Dan Williams , Thomas Gleixner , Linus Torvalds , linux-nvdimm References: <54E1CF5B.9020905@plexistor.com> In-Reply-To: <54E1CF5B.9020905@plexistor.com> Cc: "H. Peter Anvin" Subject: [Linux-nvdimm] [RFC 2/2] e820: Add the NvDIMM Memory type (type-12) X-BeenThere: linux-nvdimm@lists.01.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Linux-nvdimm developer list." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, T_RP_MATCHES_RCVD, UNPARSEABLE_RELAY autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on mail.kernel.org X-Virus-Scanned: ClamAV using ClamSMTP 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 --- 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; }