From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.4] salinfo patch
Date: Wed, 24 Dec 2003 06:26:38 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107224725703464@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107214192720071@msgid-missing>
On Tue, 23 Dec 2003 17:37:48 -0800,
Ben Woodard <ben@zork.net> wrote:
>Wouldn't a better way to fix this potential problem to add:
>...
>That way each and every ia64_sal_get_state_info() has a corresponding
>ia64_sal_clear_state_info().
The idea is right, the patch needed a bit of cleaning up.
Bjorn/DavidM, please apply, the patch fits both 2.4 and 2.6 (with
offsets). Credit to Ben Woodard <ben@zork.net>.
Avoid double clear of CMC/CPE records.
--- linux/arch/ia64/kernel/salinfo.c Wed Dec 24 17:16:12 2003
+++ linux/arch/ia64/kernel/salinfo.c Wed Dec 24 17:15:08 2003
@@ -356,6 +356,8 @@
{
struct salinfo_data *data = context;
data->log_size = ia64_sal_get_state_info(data->type, (u64 *) data->log_buffer);
+ if (data->type = SAL_INFO_TYPE_CPE || data->type = SAL_INFO_TYPE_CMC)
+ ia64_sal_clear_state_info(data->type);
}
static void
@@ -448,8 +450,11 @@
data->saved_num = 0;
spin_unlock_irqrestore(&data_saved_lock, flags);
}
- call_on_cpu(cpu, salinfo_log_clear_cpu, data);
-
+ /* ia64_mca_log_sal_error_record or salinfo_log_read_cpu already cleared
+ * CPE and CMC errors
+ */
+ if (data->type != SAL_INFO_TYPE_CPE && data->type != SAL_INFO_TYPE_CMC)
+ call_on_cpu(cpu, salinfo_log_clear_cpu, data);
/* clearing a record may make a new record visible */
salinfo_log_new_read(cpu, data);
if (data->state = STATE_LOG_RECORD &&
prev parent reply other threads:[~2003-12-24 6:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 1:04 [PATCH 2.4] salinfo patch Ben Woodard
2003-12-23 2:12 ` Keith Owens
2003-12-24 1:37 ` Ben Woodard
2003-12-24 6:26 ` Keith Owens [this message]
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-107224725703464@msgid-missing \
--to=kaos@sgi.com \
--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