From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 904CE2117FD7D for ; Fri, 26 Oct 2018 06:58:10 -0700 (PDT) Subject: Re: [PATCH 0/9] Allow persistent memory to be used like normal RAM References: <20181022201317.8558C1D8@viggo.jf.intel.com> <352acc87-a6da-65e4-bbe6-0dbffdc72acc@gmail.com> From: Dave Hansen Message-ID: Date: Fri, 26 Oct 2018 06:58:08 -0700 MIME-Version: 1.0 In-Reply-To: <352acc87-a6da-65e4-bbe6-0dbffdc72acc@gmail.com> Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Xishi Qiu , Dan Williams , Dave Hansen Cc: Tom Lendacky , Michal Hocko , Xishi Qiu , linux-nvdimm , "Huang, Ying" , Linux Kernel Mailing List , Linux MM , zy107165@alibaba-inc.com, zwisler@kernel.org, Andrew Morton , Fengguang Wu List-ID: On 10/26/18 1:03 AM, Xishi Qiu wrote: > How about let the BIOS report a new type for kmem in e820 table? > e.g. > #define E820_PMEM 7 > #define E820_KMEM 8 It would be best if the BIOS just did this all for us. But, what you're describing would take years to get from concept to showing up in someone's hands. I'd rather not wait. Plus, doing it the way I suggested gives the OS the most control. The BIOS isn't in the critical path to do the right thing. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm