From: Corey Minyard <minyard@acm.org>
To: Matt Porter <mporter@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Change to allow signal handlers to set SE and BE bits.
Date: Thu, 04 Sep 2003 09:16:56 -0500 [thread overview]
Message-ID: <3F574958.4090402@acm.org> (raw)
In-Reply-To: <20030829131824.B18608@home.com>
Actually, using the SE bit may not be the best way to handle this to
cover all the PPC variants.
Would it be better to have a special bit field someplace that is used to
communicate between the signal handler and the kernel? Some
possibilities are:
* The top 16 bits of the trap field
* The currently unused mq field (except on APUS?)
* A new field in the signal frame
I'm thinking that reserving the top 16 bits of the trap field may be the
best. It would always come in as zero (so existing software won't be
broken) and it will be available for all processors and will not be used
for anything else by the processor.
Any thoughts?
-Corey
Matt Porter wrote:
>On Fri, Aug 29, 2003 at 03:00:51PM -0500, Corey Minyard wrote:
>
>
>>I have a debugger that runs in an application that requires access to
>>the SE and BE bits. The following patch adds that capability to
>>2.4.21-ben1. I have tested this, and gdb still seems to correctly step
>>out of signal handlers, and it seems to work for 4xx. Does this look ok?
>>
>>
>
>Please change MSR_SE->MSR_DWE in the 4xx-specific sections. Also,
>a comment should be added to each generic section use of MSR_SE to
>make it clear that this is the BookE/4xx MSR_DWE.
>
>-Matt
>
>
>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-04 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 20:00 Change to allow signal handlers to set SE and BE bits Corey Minyard
2003-08-29 20:18 ` Matt Porter
2003-09-04 14:16 ` Corey Minyard [this message]
2003-09-05 15:23 ` Corey Minyard
2003-09-09 19:19 ` Corey Minyard
2003-09-09 19:39 ` Benjamin Herrenschmidt
2003-09-09 21:34 ` Corey Minyard
2003-09-10 1:37 ` Paul Mackerras
2003-09-10 2:47 ` Corey Minyard
2003-08-30 0:29 ` Paul Mackerras
2003-09-01 20:46 ` Corey Minyard
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=3F574958.4090402@acm.org \
--to=minyard@acm.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mporter@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).