Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1483683 > unrolled thread

[PATCH V2 0/2] Correct AER severity for printing AER information

Started byTyler Baicar <tbaicar@codeaurora.org>
First post2016-09-14 23:20 +0200
Last post2016-09-21 02:30 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH V2 0/2] Correct AER severity for printing AER information Tyler Baicar <tbaicar@codeaurora.org> - 2016-09-14 23:20 +0200
    [PATCH V2 2/2] acpi: apei: send correct severity to calculate AER severity Tyler Baicar <tbaicar@codeaurora.org> - 2016-09-14 23:20 +0200
    Re: [PATCH V2 0/2] Correct AER severity for printing AER information Bjorn Helgaas <helgaas@kernel.org> - 2016-09-20 21:50 +0200
      Re: [PATCH V2 0/2] Correct AER severity for printing AER information "Rafael J. Wysocki" <rjw@rjwysocki.net> - 2016-09-21 02:30 +0200

#1483683 — [PATCH V2 0/2] Correct AER severity for printing AER information

FromTyler Baicar <tbaicar@codeaurora.org>
Date2016-09-14 23:20 +0200
Subject[PATCH V2 0/2] Correct AER severity for printing AER information
Message-ID<shpL3-6a4-9@gated-at.bofh.it>
AER severity handling has two issues that cause the AER information to
be printed incorrectly. The first issue is that the function to calculate
the AER severity is called twice in the code path to print the AER
information. The second issue is that the original call to calculate the
AER severity expects the CPER severity but is recieving the GHES
severity.

V2: Fix minor typo in commit text.

V1: https://lkml.org/lkml/2016/9/12/1075

Tyler Baicar (2):
  PCI/AER: Remove duplicate AER severity translation
  acpi: apei: send correct severity to calculate AER severity

 drivers/acpi/apei/ghes.c               | 2 +-
 drivers/pci/pcie/aer/aerdrv_errprint.c | 6 ++----
 include/linux/aer.h                    | 2 +-
 3 files changed, 4 insertions(+), 6 deletions(-)

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

[toc] | [next] | [standalone]


#1483684 — [PATCH V2 2/2] acpi: apei: send correct severity to calculate AER severity

FromTyler Baicar <tbaicar@codeaurora.org>
Date2016-09-14 23:20 +0200
Subject[PATCH V2 2/2] acpi: apei: send correct severity to calculate AER severity
Message-ID<shpL3-6a4-13@gated-at.bofh.it>
In reply to#1483683
Currently the AER severity is calculated by calling
cper_severity_to_aer(), but the parameter sent is actually the
GHES severity. This causes the AER severity to be incorrect.
Fix the parameter to be the CPER severity instead of the GHES
severity.

Signed-off-by: Tyler Baicar <tbaicar@codeaurora.org>
Reviewed-by: Borislav Petkov <bp@suse.de>
---
 drivers/acpi/apei/ghes.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
index 60746ef..f0a029e 100644
--- a/drivers/acpi/apei/ghes.c
+++ b/drivers/acpi/apei/ghes.c
@@ -457,7 +457,7 @@ static void ghes_do_proc(struct ghes *ghes,
 
 				devfn = PCI_DEVFN(pcie_err->device_id.device,
 						  pcie_err->device_id.function);
-				aer_severity = cper_severity_to_aer(sev);
+				aer_severity = cper_severity_to_aer(gdata->error_severity);
 
 				/*
 				 * If firmware reset the component to contain
-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

[toc] | [prev] | [next] | [standalone]


#1487572

FromBjorn Helgaas <helgaas@kernel.org>
Date2016-09-20 21:50 +0200
Message-ID<sjzdg-7hU-35@gated-at.bofh.it>
In reply to#1483683
On Wed, Sep 14, 2016 at 03:14:44PM -0600, Tyler Baicar wrote:
> AER severity handling has two issues that cause the AER information to
> be printed incorrectly. The first issue is that the function to calculate
> the AER severity is called twice in the code path to print the AER
> information. The second issue is that the original call to calculate the
> AER severity expects the CPER severity but is recieving the GHES
> severity.
> 
> V2: Fix minor typo in commit text.
> 
> V1: https://lkml.org/lkml/2016/9/12/1075
> 
> Tyler Baicar (2):
>   PCI/AER: Remove duplicate AER severity translation
>   acpi: apei: send correct severity to calculate AER severity
> 
>  drivers/acpi/apei/ghes.c               | 2 +-
>  drivers/pci/pcie/aer/aerdrv_errprint.c | 6 ++----
>  include/linux/aer.h                    | 2 +-
>  3 files changed, 4 insertions(+), 6 deletions(-)

I applied both to pci/aer for v4.9, thanks!

Rafael, the second one is strictly ACPI, and I'd be happy to let you
deal with it if you prefer.

Bjorn

[toc] | [prev] | [next] | [standalone]


#1487736

From"Rafael J. Wysocki" <rjw@rjwysocki.net>
Date2016-09-21 02:30 +0200
Message-ID<sjDAe-1MD-11@gated-at.bofh.it>
In reply to#1487572
On Tuesday, September 20, 2016 02:41:03 PM Bjorn Helgaas wrote:
> On Wed, Sep 14, 2016 at 03:14:44PM -0600, Tyler Baicar wrote:
> > AER severity handling has two issues that cause the AER information to
> > be printed incorrectly. The first issue is that the function to calculate
> > the AER severity is called twice in the code path to print the AER
> > information. The second issue is that the original call to calculate the
> > AER severity expects the CPER severity but is recieving the GHES
> > severity.
> > 
> > V2: Fix minor typo in commit text.
> > 
> > V1: https://lkml.org/lkml/2016/9/12/1075
> > 
> > Tyler Baicar (2):
> >   PCI/AER: Remove duplicate AER severity translation
> >   acpi: apei: send correct severity to calculate AER severity
> > 
> >  drivers/acpi/apei/ghes.c               | 2 +-
> >  drivers/pci/pcie/aer/aerdrv_errprint.c | 6 ++----
> >  include/linux/aer.h                    | 2 +-
> >  3 files changed, 4 insertions(+), 6 deletions(-)
> 
> I applied both to pci/aer for v4.9, thanks!
> 
> Rafael, the second one is strictly ACPI, and I'd be happy to let you
> deal with it if you prefer.

It can go in via PCI I think.  Either way is fine by me actually. :-)

Thanks,
Rafael

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web