From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933623AbeB1TVw (ORCPT ); Wed, 28 Feb 2018 14:21:52 -0500 Received: from mx2.suse.de ([195.135.220.15]:43077 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933426AbeB1TVs (ORCPT ); Wed, 28 Feb 2018 14:21:48 -0500 Date: Wed, 28 Feb 2018 20:21:44 +0100 From: Jean Delvare To: "Rafael J. Wysocki" Cc: Andy Shevchenko , Bjorn Helgaas , Linux PCI , "Rafael J. Wysocki" , ACPI Devel Maling List , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "the arch/x86 maintainers" , Linux Kernel Mailing List Subject: Re: [PATCH v1 2/4] x86/pci: Re-use new dmi_get_bios_year() helper Message-ID: <20180228202144.2ae8149f@endymion> In-Reply-To: References: <20180222125923.57385-1-andriy.shevchenko@linux.intel.com> <20180222125923.57385-2-andriy.shevchenko@linux.intel.com> <20180226172832.7bf82336@endymion> <1519813744.10722.258.camel@linux.intel.com> Organization: SUSE Linux X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 28 Feb 2018 11:33:39 +0100, Rafael J. Wysocki wrote: > On Wed, Feb 28, 2018 at 11:29 AM, Andy Shevchenko > wrote: > > I would assume that no BIOS date is related to prehistoric firmwares and > > using _CRS would sound weird on them. > > Careful here. > > You seem to be assuming that the DMI information is always valid > and/or complete which is know to not be the case sometimes. True. While the BIOS date is not the worst offender when it comes to broken DMI data, you must remember that the date comes as a string, and older SMBIOS specifications did not even recommend a specific format for that string. As a matter of fact, my collection of DMI tables includes a few creative samples like "Jul 7 2016" or "09-16-08" which the kernel fails to parse. So the default behavior at the driver level shouldn't be based on what older systems are most likely to enjoy. The default behavior must be the safest option, regardless of the age of the system. -- Jean Delvare SUSE L3 Support