Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751973AbbBXHiW (ORCPT ); Tue, 24 Feb 2015 02:38:22 -0500 Received: from mail-wg0-f51.google.com ([74.125.82.51]:44295 "EHLO mail-wg0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880AbbBXHiV (ORCPT ); Tue, 24 Feb 2015 02:38:21 -0500 Message-ID: <54EC2A69.1070308@plexistor.com> Date: Tue, 24 Feb 2015 09:38:17 +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: Andy Lutomirski CC: Ingo Molnar , Ross Zwisler , X86 ML , linux-kernel , "Roger C. Pao" , Dan Williams , Thomas Gleixner , Linus Torvalds , linux-nvdimm , "H. Peter Anvin" , Matthew Wilcox , Christoph Hellwig Subject: Re: [PATCH 3B/3 fat] e820: dynamic unknown-xxx names (for DDR3-NvDIMM) References: <54EB1D33.3050107@plexistor.com> <54EB219F.5050706@plexistor.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2345 Lines: 63 On 02/23/2015 05:49 PM, Andy Lutomirski wrote: > On Mon, Feb 23, 2015 at 4:48 AM, Boaz Harrosh wrote: >> >> 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 BIOS vendors I know of, tagged these chips at e820 table >> as type-12 memory. >> >> 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 only be defined for DDR4. So DDR3 NvDIMM is >> probably stuck with this none STD type. >> >> I Wish and call the ACPI comity to Define that NvDIMM is type-12. >> Also for DDR4 >> >> In this patch I dynamically sprintf names into a static buffer >> (max two unknown names) of the form "unknown-XXX" where XXX >> is the type number. This is so we can return static string to >> caller. > > I prefer the other variant. > Me too > For Pete's sake, people, defining new e820 types is ludicrous. It's > already sort of happened for nvdimms (and I really hope that type 12 > is on its way out), and if it every happens again, we can deal with it > them. > No, you are wrong sir. What we need to do is define an open system. e820 is just a table that communicates between the firmware and the Kernel of the results of the DDR bus scan. Now I bet the same DDR buses are scanned much differently on other ARCHs. It is only the forsaken x86 that caries the BIOS baggage, (for economical reasons BTW, not technical) Fine I'm not going to fight that fight, but the BIOS should Just ID the devices say VENDOR/DEVICE like the PCI does. Or string ID like USB, or a UUID, and the BAR it is using and get out of the way for real drivers. I have seen DDR cards with processors on them, and all systems, and weird combinations of flashes and RAMs, and batteries, you name it. It should be easy for new devices to be added, without a single committee (God how many double letters in this word) > --Andy > Cheers Boaz -- 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/