All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: David Daney <ddaney@avtrex.com>,
	Franck Bui-Huu <vagabon.xyz@gmail.com>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: Question about signal syscalls !
Date: Mon, 5 Feb 2007 01:10:48 +0000	[thread overview]
Message-ID: <20070205011048.GA26654@linux-mips.org> (raw)
In-Reply-To: <20070205005516.GA1581@nevyn.them.org>

On Sun, Feb 04, 2007 at 07:55:16PM -0500, Daniel Jacobowitz wrote:

> On Fri, Feb 02, 2007 at 12:41:07PM -0800, David Daney wrote:
> > I thought you were suggesting not saving s0-s7.  If you don't save them, 
> > you cannot restore them.  And they have to be restored from the 
> > sigcontext in the user's address space.   This allows user space signal 
> > handlers to emulate trapping instructions, and the like.
> 
> Not necessarily, because you can trust the signal handler to restore
> them, and it can save them itself if it needs to.  As I said, I think
> there's at least one architecture which does it this way.  I'm afraid I
> don't know which one.

Not saving the s-registers into the signal frame would be a neat
optimization.  It wouldn't only make things a little faster it would
also free space in the signal frame which is needed for CPU
architecture extensions that have more state to save.  I had to burn
almost the entire available space for the DSP extensions, so I wonder
if we could get GDB to work?  The alternative is probably a new version
of the sigrestore.

  Ralf

  reply	other threads:[~2007-02-05  1:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 10:43 Question about signal syscalls ! Franck Bui-Huu
2007-02-01 13:57 ` Ralf Baechle
2007-02-01 14:54   ` Franck Bui-Huu
2007-02-01 17:01     ` David Daney
2007-02-02  8:55       ` Franck Bui-Huu
2007-02-02 16:04         ` David Daney
2007-02-02 16:36           ` Franck Bui-Huu
2007-02-02 16:53             ` Daniel Jacobowitz
2007-02-02 20:03               ` Franck Bui-Huu
2007-02-02 20:18               ` Franck Bui-Huu
2007-02-02 16:56             ` David Daney
2007-02-02 19:58               ` Franck Bui-Huu
2007-02-02 20:41                 ` David Daney
2007-02-05  0:55                   ` Daniel Jacobowitz
2007-02-05  1:10                     ` Ralf Baechle [this message]
2007-02-05  2:30                       ` Daniel Jacobowitz
2007-02-05  6:00                         ` David Daney
2007-02-05  9:17                         ` Franck Bui-Huu
2007-02-05  9:08                       ` Franck Bui-Huu
2007-02-01 18:10     ` Ralf Baechle
2007-02-02  8:54       ` Franck Bui-Huu

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=20070205011048.GA26654@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=dan@debian.org \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=vagabon.xyz@gmail.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 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.