From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752758AbbBSKCA (ORCPT <rfc822;w@1wt.eu>);
	Thu, 19 Feb 2015 05:02:00 -0500
Received: from mail-wg0-f43.google.com ([74.125.82.43]:59765 "EHLO
	mail-wg0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752323AbbBSKB6 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Thu, 19 Feb 2015 05:01:58 -0500
Date: Thu, 19 Feb 2015 11:01:51 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>, Boaz Harrosh <boaz@plexistor.com>,
        Matthew Wilcox <willy@linux.intel.com>, 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>,
        Thomas Gleixner <tglx@linutronix.de>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        linux-nvdimm <linux-nvdimm@ml01.01.org>,
        "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [Linux-nvdimm] [PATCH 0/2] e820: Fix handling of NvDIMM chips
Message-ID: <20150219100151.GA591@gmail.com>
References: <54E1CF5B.9020905@plexistor.com>
 <20150216220302.GF3364@wil.cx>
 <54E2FEF2.8060701@plexistor.com>
 <CAPcyv4if=9Cv__4D0oE9ds1C37TRDkURSVtyB8_k9Nc3WUwbrg@mail.gmail.com>
 <20150219004731.GA5477@infradead.org>
 <CAPcyv4jaqqgvjQC+QKvUohM7mAXAsZKbKntCEaiTozCCqwmFyA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPcyv4jaqqgvjQC+QKvUohM7mAXAsZKbKntCEaiTozCCqwmFyA@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Dan Williams <dan.j.williams@intel.com> wrote:

> On Wed, Feb 18, 2015 at 4:47 PM, Christoph Hellwig <hch@infradead.org> wrote:
> > On Wed, Feb 18, 2015 at 10:15:32AM -0800, Dan Williams wrote:
> >> In fact it was originally "type-6" until ACPI 5 
> >> claimed that number for official use, so these 
> >> platforms, with early proof-of-concept nvdimm support, 
> >> have already gone through one transition to a new 
> >> number.  They need to do the same once an official 
> >> number for nvdimm support is published.
> >>
> >> Put another way, these early platforms are already 
> >> using out-of-tree patches for nvdimm enabling.  They 
> >> can continue to do so, or switch to standard methods 
> >> when the standard is published.
> >
> > Not supporting hardware that is widely avaiable (I have 
> > some, too) is not very user friendly.
> 
> Yes, as I agreed with Ingo, allowing a driver to assume 
> control of an unknown memory type with a warning or a 
> kernel taint seems fine.

If someone cooks up such a patch I can apply it.

Thanks,

	Ingo