All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] fpswa logging redux
Date: Wed, 11 Dec 2002 23:42:52 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805550@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805545@msgid-missing>

>>>>> On Wed, 11 Dec 2002 14:25:14 -0800, Jesse Barnes <jbarnes@sgi.com> said:

  Jesse> I'd like to fully decode the information in the isr about
  Jesse> what type of fault occured (whether it be a software assist
  Jesse> fault, some sort of IEEE filter fault, etc.) and print it
  Jesse> along with the ip when faults occur.  While I'm at it, I may
  Jesse> as well the proper SIGFPE subcode into si_info in case of
  Jesse> signal delivery is selected.

Like Keith, I'd like to keep the amount of decoding in the kernel as
minimal as possible.  We already have si_isr in the siginfo structure,
so apps/libraries can decode things themselves.  Having said that, we
ought to decode things sufficiently so that si_code can be set to the
correct value (where this makes sense).  Hopefully, that won't add
tons of code and it would help application portability.

	--david


  parent reply	other threads:[~2002-12-11 23:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 22:25 [Linux-ia64] fpswa logging redux Jesse Barnes
2002-12-11 23:07 ` Keith Owens
2002-12-11 23:12 ` Jesse Barnes
2002-12-11 23:17 ` Keith Owens
2002-12-11 23:26 ` Jesse Barnes
2002-12-11 23:42 ` David Mosberger [this message]
2002-12-12 18:25 ` Jesse Barnes
2002-12-12 19:14 ` David Mosberger

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=marc-linux-ia64-105590709805550@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.