Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754124AbcJNJlj (ORCPT ); Fri, 14 Oct 2016 05:41:39 -0400 Received: from fw-tnat.cambridge.arm.com ([217.140.96.140]:16367 "EHLO cam-smtp0.cambridge.arm.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752729AbcJNJlV (ORCPT ); Fri, 14 Oct 2016 05:41:21 -0400 From: Punit Agrawal To: "Baicar\, Tyler" Cc: linux-efi@vger.kernel.org, matt@codeblueprint.co.uk, catalin.marinas@arm.com, will.deacon@arm.com, robert.moore@intel.com, paul.gortmaker@windriver.com, lv.zheng@intel.com, kvmarm@lists.cs.columbia.edu, fu.wei@linaro.org, "Jonathan \(Zhixiong\) Zhang" , linux@armlinux.org.uk, linux-acpi@vger.kernel.org, shijie.huang@arm.com, lenb@kernel.org, marc.zyngier@arm.com, tomasz.nowicki@linaro.org, Naveen Kaje , rostedt@goodmis.org, sandeepa.s.prabhu@gmail.com, Dkvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devel@acpica.org, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, pbonzini@redhat.com, akpm@linux-foundation.org, bristot@redhat.com Subject: Re: [PATCH V3 05/10] acpi: apei: handle SEA notification type for ARMv8 References: <1475875882-2604-1-git-send-email-tbaicar@codeaurora.org> <1475875882-2604-6-git-send-email-tbaicar@codeaurora.org> <87shs1sb1b.fsf@e105922-lin.cambridge.arm.com> <90d13241-d6b9-0b81-9f92-71df99b91b67@codeaurora.org> Date: Fri, 14 Oct 2016 10:39:50 +0100 In-Reply-To: <90d13241-d6b9-0b81-9f92-71df99b91b67@codeaurora.org> (Tyler Baicar's message of "Thu, 13 Oct 2016 08:03:55 -0600") Message-ID: <874m4fs1zt.fsf@e105922-lin.cambridge.arm.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2705 Lines: 88 "Baicar, Tyler" writes: > Hello Punit, > > > On 10/12/2016 12:00 PM, Punit Agrawal wrote: >> Tyler Baicar writes: >> >>> ARM APEI extension proposal added SEA (Synchrounous External >>> Abort) notification type for ARMv8. >>> Add a new GHES error source handling function for SEA. If an error >>> source's notification type is SEA, then this function can be registered >>> into the SEA exception handler. That way GHES will parse and report >>> SEA exceptions when they occur. >>> >>> Signed-off-by: Jonathan (Zhixiong) Zhang >>> Signed-off-by: Tyler Baicar >>> Signed-off-by: Naveen Kaje >> This patch fails to apply for me on v4.8. Is there a different tree this >> is based on? > This patch was giving me some grief as well. I'm not sure why that is > because this patchset was based on the 4.8 kernel with the dependent > patch for initial APEI support. That explains it!. I've missed out the dependency called out in the cover letter. >> One comment below. >> >> [...] >> >>> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c >>> index c8488f1..28d5a09 100644 >>> --- a/drivers/acpi/apei/ghes.c >>> +++ b/drivers/acpi/apei/ghes.c >>> @@ -50,6 +50,10 @@ >>> #include >>> #include >>> +#ifdef CONFIG_HAVE_ACPI_APEI_SEA >>> +#include >>> +#endif >>> + >>> #include "apei-internal.h" >>> #define GHES_PFX "GHES: " >>> @@ -779,6 +783,62 @@ static struct notifier_block ghes_notifier_sci = { >>> .notifier_call = ghes_notify_sci, >>> }; >>> +#ifdef CONFIG_HAVE_ACPI_APEI_SEA >>> +static LIST_HEAD(ghes_sea); >>> + >>> +static int ghes_notify_sea(struct notifier_block *this, >>> + unsigned long event, void *data) >>> +{ >>> + struct ghes *ghes; >>> + int ret = NOTIFY_DONE; >>> + >>> + rcu_read_lock(); >>> + list_for_each_entry_rcu(ghes, &ghes_sea, list) { >>> + if (!ghes_proc(ghes)) >>> + ret = NOTIFY_OK; >> Not something you've introduced but it looks like ghes_proc erroneously >> never returns anything other than 0. I plan to post the below fix to >> address it. >> >> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c >> index 60746ef..caea575 100644 >> --- a/drivers/acpi/apei/ghes.c >> +++ b/drivers/acpi/apei/ghes.c >> @@ -662,7 +662,7 @@ static int ghes_proc(struct ghes *ghes) >> ghes_do_proc(ghes, ghes->estatus); >> out: >> ghes_clear_estatus(ghes); >> - return 0; >> + return rc; >> } > Yes, this definitely should be fixed :) > > Thanks, > Tyler >>> + } >>> + rcu_read_unlock(); >>> + >>> + return ret; >>> +} >>> + >> [...] >>