Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752773AbbDBTvb (ORCPT ); Thu, 2 Apr 2015 15:51:31 -0400 Received: from mail-lb0-f176.google.com ([209.85.217.176]:35870 "EHLO mail-lb0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751125AbbDBTv1 (ORCPT ); Thu, 2 Apr 2015 15:51:27 -0400 MIME-Version: 1.0 In-Reply-To: <20150402191352.GA10627@gmail.com> References: <1427872339-6688-2-git-send-email-hch@lst.de> <20150402191352.GA10627@gmail.com> From: Andy Lutomirski Date: Thu, 2 Apr 2015 12:51:05 -0700 Message-ID: Subject: Re: [tip:x86/pmem] x86/mm: Add support for the non-standard protected e820 type To: Ingo Molnar Cc: axboe@fb.com, Boaz Harrosh , Dan Williams , "H. Peter Anvin" , Jens Axboe , "linux-kernel@vger.kernel.org" , Thomas Gleixner , Borislav Petkov , Andrew Morton , Linus Torvalds , Christoph Hellwig , Ross Zwisler , Matthew Wilcox , keith.busch@intel.com, "linux-tip-commits@vger.kernel.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1768 Lines: 51 On Thu, Apr 2, 2015 at 12:13 PM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> On Thu, Apr 2, 2015 at 5:31 AM, tip-bot for Christoph Hellwig >> wrote: >> > Commit-ID: ec776ef6bbe1734c29cd6bd05219cd93b2731bd4 >> > Gitweb: http://git.kernel.org/tip/ec776ef6bbe1734c29cd6bd05219cd93b2731bd4 >> > Author: Christoph Hellwig >> > AuthorDate: Wed, 1 Apr 2015 09:12:18 +0200 >> > Committer: Ingo Molnar >> > CommitDate: Wed, 1 Apr 2015 17:02:43 +0200 >> > >> > x86/mm: Add support for the non-standard protected e820 type >> > >> > Various recent BIOSes support NVDIMMs or ADR using a >> > non-standard e820 memory type, and Intel supplied reference >> > Linux code using this type to various vendors. >> > >> > Wire this e820 table type up to export platform devices for the >> > pmem driver so that we can use it in Linux. >> >> This scares me a bit. Do we know that the upcoming ACPI 6.0 >> enumeration mechanism *won't* use e820 type 12? [...] > > So I know nothing about it, but I'd be surprised if e820 was touched > at all, as e820 isn't really well suited to enumerate more complex > resources, and it appears pmem wants to grow into complex directions? I hope so, but I have no idea what the ACPI committee's schemes are. We could require pmem.enable_legacy_e820=Y to load the driver for now if we're concerned about it. --Andy > > Thanks, > > Ingo -- Andy Lutomirski AMA Capital Management, LLC -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/