All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Stuart Yoder <b08248@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org, Jia Hongtao <B38951@freescale.com>
Subject: Re: [PATCH V4] powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx
Date: Mon, 4 Mar 2013 17:45:44 -0600	[thread overview]
Message-ID: <1362440744.16575.6@snotra> (raw)
In-Reply-To: <CALRxmdBjb+TrqZ_XdNjH=oDcdYtVJ5=Q71dcCkKodpe7WCHDpA@mail.gmail.com> (from b08248@gmail.com on Mon Mar  4 10:16:10 2013)

On 03/04/2013 10:16:10 AM, Stuart Yoder wrote:
> On Mon, Mar 4, 2013 at 2:40 AM, Jia Hongtao <B38951@freescale.com> =20
> wrote:
> > A PCIe erratum of mpc85xx may causes a core hang when a link of PCIe
> > goes down. when the link goes down, Non-posted transactions issued
> > via the ATMU requiring completion result in an instruction stall.
> > At the same time a machine-check exception is generated to the core
> > to allow further processing by the handler. We implements the =20
> handler
> > which skips the instruction caused the stall.
>=20
> Can you explain at a high level how just skipping an instruction =20
> solves
> anything?   If you just skip a load/store and continue like nothing is
> wrong, isn't your system possibly in a really bad state.

If the instruction was a load, we probably at least want to fill the =20
destination register with 0xffffffff or similar.

> And if the core is already hung, due to the PCI link going down, isn't
> it too late?   How does skipping help?

Maybe the machine check unhangs the core?

Is there an erratum number for this?

-Scott=

  reply	other threads:[~2013-03-04 23:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  8:40 [PATCH V4] powerpc/85xx: Add machine check handler to fix PCIe erratum on mpc85xx Jia Hongtao
2013-03-04 16:16 ` Stuart Yoder
2013-03-04 23:45   ` Scott Wood [this message]
2013-03-05 10:12     ` Jia Hongtao-B38951
2013-03-05 18:47       ` Scott Wood
2013-03-06  8:28         ` Jia Hongtao-B38951
2013-03-06 10:24           ` David Laight
2013-03-07  8:06             ` Jia Hongtao-B38951
2013-03-07 10:04               ` David Laight
2013-03-07 16:37               ` Scott Wood
2013-03-08  8:01                 ` Jia Hongtao-B38951
2013-03-09  0:49                   ` Scott Wood
2013-03-12  7:40                     ` Jia Hongtao-B38951
2013-03-12  9:47                       ` David Laight
2013-03-12 21:24                       ` Scott Wood
2013-03-13  9:40                         ` David Laight
2013-03-13 16:37                           ` Scott Wood
2013-03-15  2:47                             ` Jia Hongtao-B38951
2013-03-15 16:34                               ` Scott Wood
2013-03-29  8:03                                 ` Jia Hongtao-B38951
2013-03-29 16:33                                   ` Scott Wood
2013-04-02  9:28                                     ` Jia Hongtao-B38951
2013-04-02 19:46                                       ` Scott Wood
2013-03-04 17:15 ` David Laight
2013-03-05 10:12   ` Jia Hongtao-B38951

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=1362440744.16575.6@snotra \
    --to=scottwood@freescale.com \
    --cc=B38951@freescale.com \
    --cc=b08248@gmail.com \
    --cc=linuxppc-dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.