Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rasdaemon: Do't process Ampere specific error in the public code #133

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

winterddd
Copy link

Ampere specific error info and error handler need to included in HAVE_AMP_NS_DECODE macro.

Ruidong Tian and others added 2 commits December 12, 2023 10:59
Ampere specific error info and error handler need to included in
HAVE_AMP_NS_DECODE macro.

Signed-off-by: Ruidong Tian <[email protected]>
@axiqia
Copy link

axiqia commented Dec 25, 2023

@winterddd pei_len can not decode because it is Ampere specific error.

Dec 04 11:38:42 xxxx rasdaemon[55843]: <idle>-0     [044]     0.041739: arm_event:            2023-12-04 11:38:41 +0800
Dec 04 11:38:42 xxxx rasdaemon[55843]: affinity: -1
Dec 04 11:38:42 xxxx rasdaemon[55843]: MPIDR: 0x812c0000
Dec 04 11:38:42 xxxx rasdaemon[55843]: MIDR: 0x410fd490
Dec 04 11:38:42 xxxx rasdaemon[55843]: running_state: 1
Dec 04 11:38:42 xxxx rasdaemon[55843]: psci_state: 0<CANT FIND FIELD pei_len>affinity level: 255; MPIDR: 00000000812c0000; MIDR: 00000000410fd490; running state: 1; PSCI state: 0

Could you please add details about the problem we met in commit log, so that the maintainer will see why we need this patch.

@@ -207,6 +206,9 @@ int ras_arm_event_handler(struct trace_seq *s,
ev.psci_state = val;
trace_seq_printf(s, "\n psci_state: %d", ev.psci_state);

#ifdef HAVE_AMP_NS_DECODE
int len = 0;

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coding style nit: please keep all variable declarations at the beginning of the function.

{ .name="err_info", .type="BLOB" },
{ .name="context_info", .type="BLOB" },
{ .name="vendor_info", .type="BLOB" },
#endif
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changing the DB format depending if those are declared or not sounds a bad idea, as if one recompiles the code with different options, the DB format will change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants