From: Daniel Jacobowitz <dan@debian.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: questions on struct sigcontext
Date: Wed, 12 Dec 2007 14:00:32 -0500 [thread overview]
Message-ID: <20071212190032.GA30506@caradoc.them.org> (raw)
In-Reply-To: <47601DEE.4090200@nortel.com>
On Wed, Dec 12, 2007 at 11:44:14AM -0600, Chris Friesen wrote:
>
> Hi all,
>
> First, I'm not subscribed to the list so I'd appreciate being cc'd on any
> replies.
>
> We have a project getting started with MIPS, and one of the things that
> we're trying to bring in is some exception-handling code that logs
> various information about the ways that apps fail.
>
> In particular, the guys working on this have asked for the STATUS, CAUSE,
> BADVADDR, and FPC_EIR registers to be made available as part of struct
> sigcontext so that they can determine exactly why the app is failing.
>
> Looking at include/asm-mips/sigcontext.h I can see that these registers
> appear to be in the struct, but are either marked as "unused" or now have
> different names.
>
> Am I correct that these registers are not currently exported to userspace
> on a fault? If this is the case, why not? Does anyone have a patch to
> enable this export?
There used to be slots for badvaddr and cause. You'll have to ask
Ralf why he decided to clobber them for DSP state, I don't remember
:-) I suspect they may never have held useful information for you;
we don't context switch them for userspace, so an intervening fault
in kernel space or in another thread could change them.
FPC_EIR is, unless I misremember, constant and read only. You can
just read it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-12 19:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 17:44 questions on struct sigcontext Chris Friesen
2007-12-12 18:12 ` David Daney
2007-12-12 18:34 ` Chris Friesen
2007-12-12 18:44 ` David Daney
2007-12-12 18:57 ` Ralf Baechle
2007-12-12 19:00 ` Daniel Jacobowitz [this message]
2007-12-12 19:04 ` Ralf Baechle
2007-12-12 23:47 ` Chris Friesen
2007-12-13 0:06 ` David Daney
2007-12-13 15:36 ` Daniel Jacobowitz
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=20071212190032.GA30506@caradoc.them.org \
--to=dan@debian.org \
--cc=cfriesen@nortel.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox