Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932604AbZKDVFP (ORCPT ); Wed, 4 Nov 2009 16:05:15 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932347AbZKDVFO (ORCPT ); Wed, 4 Nov 2009 16:05:14 -0500 Received: from outbound-mail-117.bluehost.com ([69.89.22.17]:57300 "HELO outbound-mail-117.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S932330AbZKDVFM convert rfc822-to-8bit (ORCPT ); Wed, 4 Nov 2009 16:05:12 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=lRoPu9sWNtvGKsSyAffbSW2pVbzd3LLZHyIANfDigJ28D857tHwCKmTGJzhb3zOOVHPLNJ7YssOb5uowqUsmtimAsWJ7fEVYcVWsiW6GHG+akETbX1LN4I4L8E+3/GnA; Date: Wed, 4 Nov 2009 13:05:15 -0800 From: Jesse Barnes To: Yinghai Lu Cc: Matt Domsch , Hidetoshi Seto , linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org, Tom Long Nguyen , Zhang Yanmin , linux-kernel@vger.kernel.org, Kenji Kaneshige , Huong_Nguyen@dell.com Subject: Re: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode Message-ID: <20091104130515.6ffb0e2b@jbarnes-piketon> In-Reply-To: <86802c440911041255i59024efckf496dfa966da8560@mail.gmail.com> References: <20091006173311.GA15751@auslistsprd01.us.dell.com> <4ACEE220.1020705@jp.fujitsu.com> <20091009182810.GB24889@mock.linuxdev.us.dell.com> <20091009183319.GC24889@mock.linuxdev.us.dell.com> <4AEA4C82.6010604@jp.fujitsu.com> <20091030025313.GA1042@mock.linuxdev.us.dell.com> <4AEA5C52.2030900@jp.fujitsu.com> <20091102175123.GA4028@mock.linuxdev.us.dell.com> <20091104091106.32489ad7@jbarnes-piketon> <86802c440911041255i59024efckf496dfa966da8560@mail.gmail.com> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.18.3; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 75.111.28.251 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2897 Lines: 66 On Wed, 4 Nov 2009 12:55:50 -0800 Yinghai Lu wrote: > On Wed, Nov 4, 2009 at 9:11 AM, Jesse Barnes > wrote: > > On Mon, 2 Nov 2009 11:51:24 -0600 > > Matt Domsch wrote: > > > >> From 97ec121f91e5c76dc037f8d2abaea84c5476676e Mon Sep 17 00:00:00 > >> 2001 From: Matt Domsch > >> Date: Thu, 8 Oct 2009 23:18:11 -0500 > >> Subject: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode > >> > >> Feedback from Hidetoshi Seto and Kenji Kaneshige incorporated. > >>  This correctly handles PCI-X bridges, PCIe root ports and > >> endpoints, and prints debug messages when invalid/reserved types > >> are found in the HEST.  PCI devices not in domain/segment 0 are > >> not represented in HEST, thus will be ignored. > >> > >> Today, the PCIe Advanced Error Reporting (AER) driver attaches > >> itself to every PCIe root port for which BIOS reports it should, > >> via ACPI _OSC. > >> > >> However, _OSC alone is insufficient for newer BIOSes.  Part of ACPI > >> 4.0 is the new APEI (ACPI Platform Error Interfaces) which is a way > >> for OS and BIOS to handshake over which errors for which components > >> each will handle.  One table in ACPI 4.0 is the Hardware Error > >> Source Table (HEST), where BIOS can define that errors for certain > >> PCIe devices (or all devices), should be handled by BIOS > >> ("Firmware First mode"), rather than be handled by the OS. > >> > >> Dell PowerEdge 11G server BIOS defines Firmware First mode in > >> HEST, so that it may manage such errors, log them to the System > >> Event Log, and possibly take other actions.  The aer driver should > >> honor this, and not attach itself to devices noted as such. > >> > >> Furthermore, Kenji Kaneshige reminded us to disallow changing the > >> AER registers when respecting Firmware First mode.  Platform > >> firmware is expected to manage these, and if changes to them are > >> allowed, it could break that firmware's behavior. > >> > >> The HEST parsing code may be replaced in the future by a more > >> feature-rich implementation.  This patch provides the minimum > >> needed to prevent breakage until that implementation is available. > >> > >> Signed-off-by: Matt Domsch > >> --- > > > > Applied to my linux-next branch, thanks. > > > > can not find acpi_hest.c and acpi_hest.h > > maybe need to wait acpi hest code is there? Arg, when I fixed up a conflict in the patch I forgot to add those files to the commit. They were in my tree so I didn't see a build error... Fixing now. -- Jesse Barnes, Intel Open Source Technology Center -- 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/