powerpc/powernv: Don't escalate non-existing frozen PE
authorGavin Shan <gwshan@linux.vnet.ibm.com>
Sun, 4 May 2014 23:29:04 +0000 (09:29 +1000)
committerBenjamin Herrenschmidt <benh@kernel.crashing.org>
Wed, 11 Jun 2014 07:04:20 +0000 (17:04 +1000)
commit71b540adffd9832e025dd9401178a8ef8c814e50
tree05c8d941e1dc8a35851db3a26222d6131014d26a
parent1ad7a72c5e57bc6a7a3190c580df14dc3642febf
powerpc/powernv: Don't escalate non-existing frozen PE

Commit cb5b242c ("powerpc/eeh: Escalate error on non-existing PE")
escalates the frozen state on non-existing PE to fenced PHB. It
was to improve kdump reliability. After that, commit 361f2a2a
("powrpc/powernv: Reset PHB in kdump kernel") was introduced to
issue complete reset on all PHBs to increase the reliability of
kdump kernel.

Commit cb5b242c becomes unuseful and it would be reverted.

Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
arch/powerpc/platforms/powernv/eeh-ioda.c