From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Preserving CMC/CPE records across reboot
Date: Fri, 13 Jan 2006 15:05:07 +0000 [thread overview]
Message-ID: <1137164707.24261.19.camel@localhost> (raw)
In-Reply-To: <14947.1137113189@ocs3.ocs.com.au>
On Fri, 2006-01-13 at 11:46 +1100, Keith Owens wrote:
>
> We should be able to keep the first few CMC/CPE records for each cpu in
> NVRAM and discard the later ones if we start getting a backlog. Then
> if the system hangs while processing a CMC/CPE, the data will still be
> available in NVRAM and will be processed on the next boot. If the
> reboot hangs again in salinfo processing then we have a solid error,
> either cpu or SAL, so switch the offending cpu out of the system.
>
> Any objections from other platforms?
Keith,
Sorry, it's been a while since I've looked at this code, but how do
we determine how many records can be stored in NVRAM? I would guess
that for CPEs at least, it's platform dependent. If it can be done w/o
losing records, it's probably ok, but I'm not sure I understand the
details. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
next prev parent reply other threads:[~2006-01-13 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 0:46 Preserving CMC/CPE records across reboot Keith Owens
2006-01-13 15:05 ` Alex Williamson [this message]
2006-01-13 15:57 ` Jack Steiner
2006-01-13 20:23 ` Luck, Tony
2006-01-14 6:50 ` 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=1137164707.24261.19.camel@localhost \
--to=alex.williamson@hp.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