From: David Gibson <redacted>
Based on patch by David Gibson [off-list ref]
xmon has a longstanding bug on systems which are SMP-capable but lack
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by ignoring
the RI bit if the processor does not support it.
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
BookE processors to the mix.
Signed-off-by: Jimi Xenidis <redacted>
---
arch/powerpc/xmon/xmon.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
@@ -340,8 +340,8 @@ int cpus_are_in_xmon(void)staticinlineintunrecoverable_excp(structpt_regs*regs){-#ifdef CONFIG_4xx-/* We have no MSR_RI bit on 4xx, so we simply return false */+#if defined(CONFIG_4xx) || defined(CONFIG_BOOKE)+/* We have no MSR_RI bit on 4xx or Book3e, so we simply return false */return0;#elsereturn((regs->msr&MSR_RI)==0);
From: Benjamin Herrenschmidt <benh@kernel.crashing.org> Date: 2011-08-30 06:11:22
On Mon, 2011-08-08 at 16:25 -0500, Jimi Xenidis wrote:
From: David Gibson <redacted>
Based on patch by David Gibson [off-list ref]
xmon has a longstanding bug on systems which are SMP-capable but lack
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by ignoring
the RI bit if the processor does not support it.
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
BookE processors to the mix.
@@ -340,8 +340,8 @@ int cpus_are_in_xmon(void)staticinlineintunrecoverable_excp(structpt_regs*regs){-#ifdef CONFIG_4xx-/* We have no MSR_RI bit on 4xx, so we simply return false */+#if defined(CONFIG_4xx) || defined(CONFIG_BOOKE)+/* We have no MSR_RI bit on 4xx or Book3e, so we simply return false */return0;#elsereturn((regs->msr&MSR_RI)==0);
From: Scott Wood <hidden> Date: 2011-08-30 18:09:18
On 08/30/2011 01:11 AM, Benjamin Herrenschmidt wrote:
On Mon, 2011-08-08 at 16:25 -0500, Jimi Xenidis wrote:
quoted
From: David Gibson <redacted>
Based on patch by David Gibson [off-list ref]
xmon has a longstanding bug on systems which are SMP-capable but lack
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by ignoring
the RI bit if the processor does not support it.
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
BookE processors to the mix.
Don't freescale one have RI ?
e500mc does.
e500v2 doesn't -- if a machine check happens while MSR[ME]=0, it causes
a checkstop.
-Scott
On 08/30/2011 01:11 AM, Benjamin Herrenschmidt wrote:
quoted
On Mon, 2011-08-08 at 16:25 -0500, Jimi Xenidis wrote:
quoted
From: David Gibson <redacted>
=20
Based on patch by David Gibson [off-list ref]
=20
xmon has a longstanding bug on systems which are SMP-capable but =
lack
quoted
quoted
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by =
ignoring
quoted
quoted
the RI bit if the processor does not support it.
=20
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
BookE processors to the mix.
=20
Don't freescale one have RI ?
=20
e500mc does.
hmm, according to the ISA, MSR[RI] is only defined for Book3s and is not =
defined for Book3e
Should we scope it to just book3e?
-jx
=20
e500v2 doesn't -- if a machine check happens while MSR[ME]=3D0, it =
From: David Gibson <redacted>
Based on patch by David Gibson [off-list ref]
xmon has a longstanding bug on systems which are SMP-capable but lack
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by ignoring
the RI bit if the processor does not support it.
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
Book3e processors to the mix.
Signed-off-by: Jimi Xenidis <redacted>
---
Restricted it to Book3e
---
arch/powerpc/xmon/xmon.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
@@ -340,8 +340,8 @@ int cpus_are_in_xmon(void)staticinlineintunrecoverable_excp(structpt_regs*regs){-#ifdef CONFIG_4xx-/* We have no MSR_RI bit on 4xx, so we simply return false */+#if defined(CONFIG_4xx) || defined(CONFIG_BOOK3E)+/* We have no MSR_RI bit on 4xx or Book3e, so we simply return false */return0;#elsereturn((regs->msr&MSR_RI)==0);
From: David Gibson <redacted>
Based on patch by David Gibson [off-list ref]
xmon has a longstanding bug on systems which are SMP-capable but lack
the MSR[RI] bit. In these cases, xmon invoked by IPI on secondary
CPUs will not properly keep quiet, but will print stuff, thereby
garbling the primary xmon's output. This patch fixes it, by ignoring
the RI bit if the processor does not support it.
There's already a version of this for 4xx upstream, which we'll need
to extend to other RI-lacking CPUs at some point. For now this adds
Book3e processors to the mix.
Signed-off-by: Jimi Xenidis <redacted>
---
Restricted it to Book3e
Fix typo, its supposed to be CONFIG_PPC_BOOK3E
---
arch/powerpc/xmon/xmon.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
@@ -340,8 +340,8 @@ int cpus_are_in_xmon(void)staticinlineintunrecoverable_excp(structpt_regs*regs){-#ifdef CONFIG_4xx-/* We have no MSR_RI bit on 4xx, so we simply return false */+#if defined(CONFIG_4xx) || defined(CONFIG_PPC_BOOK3E)+/* We have no MSR_RI bit on 4xx or Book3e, so we simply return false */return0;#elsereturn((regs->msr&MSR_RI)==0);