From: Patrick Williams <patrick@stwcx.xyz>
To: Daniel Axtens <dja@axtens.net>
Cc: mahesh@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
skiboot@lists.ozlabs.org
Subject: Re: [Skiboot] Skiboot recovery of MCEs during MMIO read of SCOMs: 55672ecfa21f
Date: Mon, 21 Sep 2015 15:01:19 -0500 [thread overview]
Message-ID: <20150921200119.GD8884@asimov.ibm.com> (raw)
In-Reply-To: <1442804568.13852.9.camel@axtens.net>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On Mon, Sep 21, 2015 at 01:02:48PM +1000, Daniel Axtens wrote:
> 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
>
> _______________________________________________
> Skiboot mailing list
> Skiboot@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/skiboot
XSCOM does not cause a machine check. Centaur Inband SCOM does cause a
machine check. Was this maybe put in place in anticipation of
supporting Inband SCOM? Does skiboot support Inband SCOM now?
--
Patrick Williams
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-09-21 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-21 3:02 Skiboot recovery of MCEs during MMIO read of SCOMs: 55672ecfa21f Daniel Axtens
2015-09-21 20:01 ` Patrick Williams [this message]
2015-09-21 21:44 ` [Skiboot] " 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=20150921200119.GD8884@asimov.ibm.com \
--to=patrick@stwcx.xyz \
--cc=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).