linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
To: "Luck, Tony" <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: "Chen, Gong" <gong.chen@linux.intel.com>,
	"joe@perches.com" <joe@perches.com>,
	"m.chehab@samsung.com" <m.chehab@samsung.com>,
	"arozansk@redhat.com" <arozansk@redhat.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 4/9] ACPI, x86: Extended error log driver for x86 platform
Date: Tue, 22 Oct 2013 15:02:17 +0530	[thread overview]
Message-ID: <52664621.8070307@linux.vnet.ibm.com> (raw)
In-Reply-To: <52657a78162905670f@agluck-desk.sc.intel.com>

On 10/22/2013 12:33 AM, Luck, Tony wrote:
>> But yes, this is possible and it would make it all even cleaner
>> and simpler by simply not needing the reg/dereg interfaces for
>> mce_ext_err_print but adding it to the chain.
>
> So this is on top of the 9 patch series (using the V4 that Chen Gong
> posted for part 4/9 and V3 for all the others).  Obviously it should
> be folded back into the series if we go this way.
>
> It's a bit simplistic right now - the registered function just returns
> NOTIFY_DONE in all cases so it will not disturb processing by any other
> registered functions - we can make it smarter later.

Looks good. We obviously need to ensure this gets called before EDAC, if 
at all. The other question is w.r.t conflicts with EDAC, which we can 
re-visit as part of the discussions around a new trace event.

Thanks,
Naveen


  parent reply	other threads:[~2013-10-22 10:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-18  8:23 [PATCH v3 0/9] Extended H/W error log driver Chen, Gong
2013-10-18  8:23 ` [PATCH v3 1/9] ACPI, APEI, CPER: Fix status check during error printing Chen, Gong
2013-10-18  8:23 ` [PATCH v3 2/9] ACPI, CPER: Update cper info Chen, Gong
2013-10-18 12:39   ` Naveen N. Rao
2013-10-18  8:23 ` [PATCH v3 3/9] bitops: Introduce a more generic BITMASK macro Chen, Gong
2013-10-18  8:23 ` [PATCH v3 4/9] ACPI, x86: Extended error log driver for x86 platform Chen, Gong
2013-10-18 12:37   ` Naveen N. Rao
2013-10-18 12:53     ` Borislav Petkov
2013-10-18 20:57       ` Luck, Tony
2013-10-18 21:27         ` Borislav Petkov
2013-10-18 22:22           ` Luck, Tony
2013-10-19  9:57             ` Borislav Petkov
2013-10-21 19:03               ` Luck, Tony
2013-10-21 22:39                 ` Tony Luck
2013-10-22  8:37                   ` Borislav Petkov
2013-10-22  9:32                 ` Naveen N. Rao [this message]
2013-10-19 11:31     ` Chen Gong
2013-10-20  7:06     ` Chen Gong
2013-10-20  8:21       ` Borislav Petkov
2013-10-21 16:27         ` Naveen N. Rao
2013-10-20  7:25     ` [PATCH V4 " Chen, Gong
2014-06-27  5:34     ` [PATCH v3 " Xie XiuQi
2014-06-27  9:22       ` Borislav Petkov
2014-06-27 20:43         ` Luck, Tony
2014-06-27 21:14           ` Borislav Petkov
2014-06-27 22:10             ` Luck, Tony
2014-06-27 22:14               ` Borislav Petkov
2014-06-30  6:35               ` Xie XiuQi
2013-10-18  8:23 ` [PATCH v3 5/9] DMI: Parse memory device (type 17) in SMBIOS Chen, Gong
2013-10-18  8:23 ` [PATCH v3 6/9] ACPI, APEI, CPER: Add UEFI 2.4 support for memory error Chen, Gong
2013-10-18  8:23 ` [PATCH v3 7/9] ACPI, APEI, CPER: Enhance memory reporting capability Chen, Gong
2013-10-18  8:23 ` [PATCH v3 8/9] ACPI, APEI, CPER: Cleanup CPER memory error output format Chen, Gong
2013-10-18 12:01   ` Naveen N. Rao
2013-10-19 11:26     ` Chen Gong
2013-10-21 16:22       ` Naveen N. Rao
2013-10-21 17:14         ` Luck, Tony
2013-10-22  8:42           ` Borislav Petkov
2013-10-18  8:23 ` [PATCH v3 9/9] EDAC, GHES: Update ghes error record info Chen, Gong
2013-10-18  9:20 ` [PATCH v3 0/9] Extended H/W error log driver Borislav Petkov
2013-10-18 16:17   ` Tony Luck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52664621.8070307@linux.vnet.ibm.com \
    --to=naveen.n.rao@linux.vnet.ibm.com \
    --cc=arozansk@redhat.com \
    --cc=bp@alien8.de \
    --cc=gong.chen@linux.intel.com \
    --cc=joe@perches.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.chehab@samsung.com \
    --cc=tony.luck@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).