public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Menyhart <Zoltan.Menyhart_AT_bull.net@nospam.org>
To: linux-ia64@vger.kernel.org
Subject: re: Rework arch/ia64/kernel/salinfo.c for 2.4
Date: Mon, 20 Oct 2003 14:38:54 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106666078703118@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106664704821234@msgid-missing>

Keith,

I did see an uncorrectable cache error (MCA) and a corrected
memory error (CMC) in a single SAL error log record.
Can you sort out such a case ?

Is there any use to show the log of INIT ?

/* save last 5 records from mca.c, must be < 255 */
struct salinfo_data: struct salinfo_data_saved data_saved[5]; :

It would be much more safe for the MCA stuff to reserve a data
buffer for each CPU. As there is no mutual exclusion with the
MCA handler:
- do not "clear" nor "shift" MCA logs
- the MCA handler can overwrite the buffer of the CPU on which
  it executes
- for the "read <n>" command, you may:
  + calculate a CRC32 of the buffer[n]
  + copy_to_user(buffer[n],...)
  + calculate again the CRC32 of the buffer[n] and restart
    if it is not the same as before

Assuming I've got a CPE, can I read its SAL log on any CPU ?
Can I clear this SAL log on a different CPU ?

If a CMC's SAL log includes some Platform ... Error Info
structures and another CPU can pinch the platform related
error information (and it can clear it too), how can the CPU
causing the error know what has happened ?

Assuming I've got a CMC / CPE, I read its log but I do not clear it.
Assuming I've got another CMC / CPE and I read the log: are the
new / old errors merged ?

Thanks,

Zoltan Menyhart

  reply	other threads:[~2003-10-20 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 10:47 Rework arch/ia64/kernel/salinfo.c for 2.4 Keith Owens
2003-10-20 14:38 ` Zoltan Menyhart [this message]
2003-10-20 14:53 ` Keith Owens
2003-10-20 23:38 ` Bjorn Helgaas
2003-10-21  0:12 ` Keith Owens
2003-10-21 11:49 ` Zoltan Menyhart
2003-10-21 11:55 ` Zoltan Menyhart
2003-10-21 12:31 ` 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-106666078703118@msgid-missing \
    --to=zoltan.menyhart_at_bull.net@nospam.org \
    --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