Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751542AbdFHRe0 (ORCPT ); Thu, 8 Jun 2017 13:34:26 -0400 Received: from mail-ot0-f178.google.com ([74.125.82.178]:34653 "EHLO mail-ot0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751382AbdFHReY (ORCPT ); Thu, 8 Jun 2017 13:34:24 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170607184947.18733-1-toshi.kani@hpe.com> <1496869051.9288.1.camel@hpe.com> <1496871186.9288.3.camel@hpe.com> From: Dan Williams Date: Thu, 8 Jun 2017 10:34:22 -0700 Message-ID: Subject: Re: [PATCH] Add support of NVDIMM memory error notification in ACPI 6.2 To: Linda Knippers Cc: "Kani, Toshimitsu" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" , "linux-acpi@vger.kernel.org" , "rjw@rjwysocki.net" , "vishal.l.verma@intel.com" 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: 727 Lines: 15 On Thu, Jun 8, 2017 at 10:30 AM, Linda Knippers wrote: [..] > Wasn't Dan concerned about how the OS can know whether the FW supports > that bit in the Start ARS? > > The Query ARS Capabilities DSM has a bit that tells the OS whether the > platform supports the notification and the point of the notification was > to tell the OS it could do a Start ARS with bit 1 set. Of course, if > you get the notification then that means the platform has the capability > to deliver it, but it might not hurt to check the flag from the Query > Capabilities bit. Good point, yes, I think it is safe to assume that a BIOS that claims to support un-correctable error notification also supports this Start ARS flag.