powerpc/xmon: Teach xmon oops about radix vectors
Currently if we take an oops caused by an 0x380 or 0x480 exception, we get a print which assumes SLB problems. With radix, these vectors have different meanings. This patch updates the oops message to reflect these different meanings. Signed-off-by: Michael Neuling <mikey@neuling.org> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
This commit is contained in:
parent
add2e1e585
commit
8915bcd68b
|
@ -1369,9 +1369,19 @@ const char *getvecname(unsigned long vec)
|
|||
case 0x100: ret = "(System Reset)"; break;
|
||||
case 0x200: ret = "(Machine Check)"; break;
|
||||
case 0x300: ret = "(Data Access)"; break;
|
||||
case 0x380: ret = "(Data SLB Access)"; break;
|
||||
case 0x380:
|
||||
if (radix_enabled())
|
||||
ret = "(Data Access Out of Range)";
|
||||
else
|
||||
ret = "(Data SLB Access)";
|
||||
break;
|
||||
case 0x400: ret = "(Instruction Access)"; break;
|
||||
case 0x480: ret = "(Instruction SLB Access)"; break;
|
||||
case 0x480:
|
||||
if (radix_enabled())
|
||||
ret = "(Instruction Access Out of Range)";
|
||||
else
|
||||
ret = "(Instruction SLB Access)";
|
||||
break;
|
||||
case 0x500: ret = "(Hardware Interrupt)"; break;
|
||||
case 0x600: ret = "(Alignment)"; break;
|
||||
case 0x700: ret = "(Program Check)"; break;
|
||||
|
|
Loading…
Reference in New Issue