From: Ralf Baechle <ralf@linux-mips.org>
To: Prasad B <bprasad@cs.arizona.edu>
Cc: linux-mips@linux-mips.org
Subject: Re: traditional signal support in 64-bit mips linux
Date: Tue, 18 Nov 2008 11:53:56 +0000 [thread overview]
Message-ID: <20081118115356.GA7700@linux-mips.org> (raw)
In-Reply-To: <e8180c7f0811171324i35da6933mc29ce386afb7393a@mail.gmail.com>
On Mon, Nov 17, 2008 at 01:24:07PM -0800, Prasad B wrote:
> Is traditional signal support, enabled by the flag CONFIG_TRAD_SIGNALS
> proscribed in 64-bit mode ?
Yes - and there is no reason to do so. None of the libcs would use the
functionality and it's not experted through the syscall interface anyway.
> In arch/mips/kernel/signal.c, functions sys_sigsuspend(), sys_sigaction(),
> sys_sigreturn(), setup_frame() are conditionally compiled, depending on
> whether the flag CONFIG_TRAD_SIGNALS is defined or not. If one defines the
> constant, the compilation fails as the constants such as __NR_sigreturn are
> not defined in asm-mips/unistd.h for 64-bit mips.
>
>
> Does it mean that only realtime signals are supposed to be used in 64-bit
> mode ?
Yes - with the exception of O32 binary compatibility which uses a compat
implementation of these functions anyway. Traditional signal support is
deprecated since like 10 years.
Ralf
prev parent reply other threads:[~2008-11-18 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 21:24 traditional signal support in 64-bit mips linux Prasad B
2008-11-18 11:53 ` Ralf Baechle [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=20081118115356.GA7700@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=bprasad@cs.arizona.edu \
--cc=linux-mips@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