From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753362AbbDBTN7 (ORCPT ); Thu, 2 Apr 2015 15:13:59 -0400 Received: from mail-wg0-f47.google.com ([74.125.82.47]:34896 "EHLO mail-wg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751433AbbDBTN5 (ORCPT ); Thu, 2 Apr 2015 15:13:57 -0400 Date: Thu, 2 Apr 2015 21:13:52 +0200 From: Ingo Molnar To: Andy Lutomirski 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" Subject: Re: [tip:x86/pmem] x86/mm: Add support for the non-standard protected e820 type Message-ID: <20150402191352.GA10627@gmail.com> References: <1427872339-6688-2-git-send-email-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * 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? Thanks, Ingo