From: Ben Woodard <ben@zork.net>
To: linux-ia64@vger.kernel.org
Subject: [PATCH 2.4] salinfo patch
Date: Tue, 23 Dec 2003 01:04:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107214192720071@msgid-missing> (raw)
It looks to me like the salinfo.c and mca.c code can try to clear CPEs
and CMCs twice the first time in ia64_mca_log_sal_error_record and then
later when the clear message is sent to the /proc/sal/{cpe,cmc}/data
file. Did I miss something?
Here is a trivially little patch that fixes it one way.
diff -u -r1.1.24.1.68.1 salinfo.c
--- salinfo.c 16 Dec 2003 22:14:31 -0000 1.1.24.1.68.1
+++ salinfo.c 23 Dec 2003 00:51:27 -0000
@@ -448,7 +450,10 @@
data->saved_num = 0;
spin_unlock_irqrestore(&data_saved_lock, flags);
}
- call_on_cpu(cpu, salinfo_log_clear_cpu, data);
+
+ if (!data->type = SAL_INFO_TYPE_CPE && !data->type = SAL_INFO_TYPE_CMC)
+ /* ia64_mca_log_sal_error_record already cleared CPE and CMC errors */
+ call_on_cpu(cpu, salinfo_log_clear_cpu, data);
/* clearing a record may make a new record visible */
salinfo_log_new_read(cpu, data);
Another way to fix it would be to remove the clearing the SAL error in
ia64_mca_log_sal_error_record. Though, I have to say I am extremely
uncomfortable depending on and waiting for something in user space to
acknowledge system problems before other errors can be reported.
While I'm at it, something that I've been completely unable to
understand is why salinfo.c provides two distinct files, event and data.
It seems like the event file is virtually useless. Why not just have the
same blocking read on the data file?
-ben
next reply other threads:[~2003-12-23 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 1:04 Ben Woodard [this message]
2003-12-23 2:12 ` [PATCH 2.4] salinfo patch Keith Owens
2003-12-24 1:37 ` Ben Woodard
2003-12-24 6:26 ` Keith Owens
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=marc-linux-ia64-107214192720071@msgid-missing \
--to=ben@zork.net \
--cc=linux-ia64@vger.kernel.org \
/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