Re: [Linux-ia64] fpswa logging redux

From: Jesse Barnes <jbarnes_at_sgi.com>
Date: 2002-12-12 10:26:08
On Thu, Dec 12, 2002 at 10:17:20AM +1100, Keith Owens wrote:
> On Wed, 11 Dec 2002 15:12:18 -0800, 
> Jesse Barnes <jbarnes@sgi.com> wrote:
> >On Thu, Dec 12, 2002 at 10:07:57AM +1100, Keith Owens wrote:
> >> I have a couple of Perl scripts for decoding isr and psr.  They read
> >> hex values (with or without the leading 0x) from stdin and pretty print
> >> the result.
> >
> >It's the isr code field I'm particularly interested in.  For fp faults
> >and traps, I'd like to decode what type of fault/trap occured and add it
> >to the printk, e.g.
> >Dec 11 17:11:05 morale kernel: a.out(1901): floating-point assist trap : ip=4000000000000752
> >Dec 11 17:11:05 morale kernel: a.out(1901): floating-point assist fault : software assist ip=4000000000000c01
> 
> The general approach is that the kernel prints raw values and user
> space decodes them, unless there is some overriding reason to do it in
> kernel.  IOW, print the isr in the kernel but decode it using the
> scripts or equivalent.

But if we do that the si_code field of siginfo won't have useful
information.  My thought was that if we decode isr in enough detail to
fill in si_code correctly, we may as well make the printks more useful
as well.  I think all this stuff would be in arch/ia64/kernel/traps.c,
with the possible exception of another SIGFPE code for software assist
faults (and maybe denormal/unnormal).

Thanks,
Jesse
Received on Wed Dec 11 15:27:44 2002

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:11 EST