From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756136Ab0KXBR2 (ORCPT ); Tue, 23 Nov 2010 20:17:28 -0500 Received: from mga11.intel.com ([192.55.52.93]:27535 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754440Ab0KXBR0 (ORCPT ); Tue, 23 Nov 2010 20:17:26 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.59,245,1288594800"; d="scan'208";a="860781786" From: Huang Ying To: Len Brown Cc: linux-kernel@vger.kernel.org, Andi Kleen , ying.huang@intel.com, linux-acpi@vger.kernel.org, Peter Zijlstra , Andrew Morton , Linus Torvalds , Ingo Molnar , Mauro Carvalho Chehab , Borislav Petkov , Thomas Gleixner Subject: [RFC][PATCH 0/3] Report APEI GHES error information via printk Date: Wed, 24 Nov 2010 09:16:51 +0800 Message-Id: <1290561414-13313-1-git-send-email-ying.huang@intel.com> X-Mailer: git-send-email 1.7.2.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Although we have no consensus on whether we need a hardware error specific reporting interface. We have the consensus that we need to report hardware error information via printk. This patchset adds that to APEI GHES. [RFC][PATCH 1/3] Add CPER PCIe error section structure and constants definition [RFC][PATCH 2/3] ACPI, APEI, Add APEI generic error status print support [RFC][PATCH 3/3] ACPI, APEI, report GHES error information via printk