From: Daniel Axtens <dja@axtens.net>
To: mahesh@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
skiboot@lists.ozlabs.org
Subject: Skiboot recovery of MCEs during MMIO read of SCOMs: 55672ecfa21f
Date: Mon, 21 Sep 2015 13:02:48 +1000 [thread overview]
Message-ID: <1442804568.13852.9.camel@axtens.net> (raw)
Hi,
This relates to 55672ecfa21f ("powerpc/book3s: Recover from MC in
sapphire on SCOM read via MMIO.").
According to that patch, some SCOM reads via MMIO could lead to a
Machine Check Error in skiboot. That patch provided kernel support for a
skiboot interface to recover from those MCEs.
That patch went into the kernel in Dec 2013. However, modern skiboot
does not expose the device tree property needed to use this mechanism.
As far as I can tell, nothing ever went into Skiboot for this purpose.
Is this something we plan to use in the future? Or is it now redundant?
--
Regards,
Daniel
next reply other threads:[~2015-09-21 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 3:02 Daniel Axtens [this message]
2015-09-21 20:01 ` [Skiboot] Skiboot recovery of MCEs during MMIO read of SCOMs: 55672ecfa21f Patrick Williams
2015-09-21 21:44 ` Benjamin Herrenschmidt
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=1442804568.13852.9.camel@axtens.net \
--to=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=skiboot@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).