From: Keith Owens <kaos@ocs.com.au>
To: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
Subject: Re: ksymoops changes for mips
Date: Wed, 27 Jun 2001 12:21:57 +1000 [thread overview]
Message-ID: <16633.993608517@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 13 Jun 2001 22:19:14 +1000." <8465.992434754@ocs4.ocs-net>
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.
next prev parent reply other threads:[~2001-06-27 2:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-10 22:03 Kernel crash on boot with current cvs (todays) Florian Lohoff
2001-06-11 3:53 ` Keith Owens
2001-06-11 19:12 ` Florian Lohoff
2001-06-12 1:01 ` Maciej W. Rozycki
2001-06-12 1:01 ` Keith M Wesolowski
2001-06-12 1:22 ` Maciej W. Rozycki
2001-06-12 2:05 ` Keith Owens
2001-06-11 4:42 ` Ralf Baechle
2001-06-11 14:50 ` Raoul Borenius
2001-06-12 10:09 ` Florian Lohoff
2001-06-12 11:53 ` Ralf Baechle
2001-06-12 16:37 ` H . J . Lu
[not found] ` <20010613100602.A17124@bunny.shuttle.de>
2001-06-13 10:56 ` Florian Lohoff
2001-06-13 11:34 ` Keith Owens
2001-06-13 12:05 ` Ralf Baechle
2001-06-13 12:19 ` ksymoops changes for mips (was Kernel crash on boot with current cvs) Keith Owens
2001-06-16 9:22 ` Ralf Baechle
2001-06-27 2:21 ` Keith Owens [this message]
2001-06-28 14:32 ` ksymoops changes for mips Thiemo Seufer
2001-07-31 3:57 ` Keith Owens
2001-07-31 4:30 ` Keith Owens
2001-08-03 6:10 ` Keith Owens
2001-08-03 10:07 ` Thiemo Seufer
2001-06-13 13:44 ` Kernel crash on boot with current cvs (todays) Maciej W. Rozycki
2001-06-13 14:07 ` Keith Owens
2001-06-13 15:08 ` Maciej W. Rozycki
2001-06-16 9:24 ` Ralf Baechle
2001-06-13 11:37 ` Raoul Borenius
2001-06-13 11:46 ` Keith Owens
2001-06-13 11:46 ` Keith Owens
2001-06-13 13:16 ` Raoul Borenius
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=16633.993608517@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox