linux-mips
[Top] [All Lists]

Re: ksymoops changes for mips

To: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: ksymoops changes for mips
From: Keith Owens <kaos@ocs.com.au>
Date: Wed, 27 Jun 2001 12:21:57 +1000
In-reply-to: Your message of "Wed, 13 Jun 2001 22:19:14 +1000." <8465.992434754@ocs4.ocs-net>
Sender: owner-linux-mips@oss.sgi.com
On Wed, 13 Jun 2001 22:19:14 +1000, 
Keith Owens <kaos@melbourne.sgi.com> wrote:
>ksymoops is designed to run on any build arch and debug an oops report
>from any other target arch, as long as binutils supports the target
>arch.  The presence or absence of __MIPSEL__ or __MIPSEB__ on the build
>system says nothing about the type of the failing target, ksymoops
>relies on text in the oops report to determine special cases like 32
>bit userland and 64 bit kernel.
>
>The best option is for a mips64 kernel to indicate that it is 64 bit
>and its endianess.  Instead of printing
>
>  "epc     : %016lx\n"
>
>print
>
>  "epc     : %016lx (64 "
>#ifdef __MIPSEL__
>               "LSB"
>#else
>               "MSB"
>#endif
>               ")\n"

I have a new ksymoops release coming up.  Is it OK if I include code to
look for (64 LSB) and (64 MSB) in the oops and decode accordingly.  I
don't expect the kernel to produce this output immediately, I just want
agreement on the format that will be produced.


<Prev in Thread] Current Thread [Next in Thread>