From: Christophe Rhodes <csr21@cam.ac.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: rth@twiddle.net, linux-kernel@vger.kernel.org
Subject: Re: SPARC and SA_SIGINFO signal handling
Date: Wed, 7 Nov 2001 09:33:18 +0000 [thread overview]
Message-ID: <20011107093318.A11078@cam.ac.uk> (raw)
In-Reply-To: <20011031094342.A27520@cam.ac.uk> <20011031.021131.74751566.davem@redhat.com> <20011103115900.B5984@twiddle.net> <20011103.155422.74749787.davem@redhat.com>
In-Reply-To: <20011103.155422.74749787.davem@redhat.com>
On Sat, Nov 03, 2001 at 03:54:22PM -0800, David S. Miller wrote:
> From: Richard Henderson <rth@twiddle.net>
> Date: Sat, 3 Nov 2001 11:59:00 -0800
>
> On Wed, Oct 31, 2001 at 02:11:31AM -0800, David S. Miller wrote:
> > The "register contents and so on" are in the sigcontext.
> > We don't use ucontext on sparc32.
>
> In other words, you don't support SA_SIGINFO at all.
>
> Is it required? All the information that thing provides is
> determinable via other methods.
Sorry for the late response (I've been away); "required" is perhaps
putting it strongly, because as you say the information is there,
somewhere. However, it would be nice to have, as standardized, that
the third argument to the sa_sigaction handler be castable to a
ucontext_t, as this would make porting signal-handling code between
Linux flavours much easier.
Cheers,
Christophe
--
Jesus College, Cambridge, CB5 8BL +44 1223 510 299
http://www-jcsu.jesus.cam.ac.uk/~csr21/ (defun pling-dollar
(str schar arg) (first (last +))) (make-dispatch-macro-character #\! t)
(set-dispatch-macro-character #\! #\$ #'pling-dollar)
prev parent reply other threads:[~2001-11-07 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 19:00 SPARC and SA_SIGINFO signal handling Christophe Rhodes
2001-10-30 20:51 ` David S. Miller
2001-10-31 9:43 ` Christophe Rhodes
2001-10-31 10:11 ` David S. Miller
2001-11-03 19:59 ` Richard Henderson
2001-11-03 23:54 ` David S. Miller
2001-11-04 17:25 ` Richard Henderson
2001-11-07 9:33 ` Christophe Rhodes [this message]
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=20011107093318.A11078@cam.ac.uk \
--to=csr21@cam.ac.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rth@twiddle.net \
/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