linux-toradex.git/arch/powerpc/kernel/signal.c, branch v3.4.2

Disintegrate asm/system.h for PowerPC

2012-03-28T17:30:02+00:00

Disintegrate asm/system.h for PowerPC.

Signed-off-by: David Howells 
Acked-by: Benjamin Herrenschmidt 
cc: linuxppc-dev@lists.ozlabs.org

powerpc: Use set_current_blocked() and block_sigmask()

2012-03-07T06:06:09+00:00

As described in e6fa16ab ("signal: sigprocmask() should do
retarget_shared_pending()") the modification of current->blocked is
incorrect as we need to check whether the signal we're about to block
is pending in the shared queue.

Also, use the new helper function introduced in commit 5e6292c0f28f
("signal: add block_sigmask() for adding sigmask to current->blocked")
which centralises the code for updating current->blocked after
successfully delivering a signal and reduces the amount of duplicate
code across architectures. In the past some architectures got this
code wrong, so using this helper function should stop that from
happening again.

Cc: Oleg Nesterov 
Cc: Benjamin Herrenschmidt 
Cc: Paul Mackerras 
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Matt Fleming 
Signed-off-by: Benjamin Herrenschmidt

powerpc: Fix various issues with return to userspace

2012-02-22T05:48:53+00:00

We have a few problems when returning to userspace. This is a
quick set of fixes for 3.3, I'll look into a more comprehensive
rework for 3.4. This fixes:

 - We kept interrupts soft-disabled when schedule'ing or calling
do_signal when returning to userspace as a result of a hardware
interrupt.

 - Rename do_signal to do_notify_resume like all other archs (and
do_signal_pending back to do_signal, which it was before Roland
changed it).

 - Add the missing call to key_replace_session_keyring() to
do_notify_resume().

Signed-off-by: Benjamin Herrenschmidt 
---

powerpc: fix double syscall restarts

2010-09-22T16:33:50+00:00

Make sigreturn zero regs->trap, make do_signal() do the same on all
paths.  As it is, signal interrupting e.g. read() from fd 512 (==
ERESTARTSYS) with another signal getting unblocked when the first
handler finishes will lead to restart one insn earlier than it ought
to.  Same for multiple signals with in-kernel handlers interrupting
that sucker at the same time.  Same for multiple signals of any kind
interrupting that sucker on 64bit...

Signed-off-by: Al Viro 
Acked-by: Paul Mackerras 
Signed-off-by: Linus Torvalds

powerpc, hw_breakpoint: Enable hw-breakpoints while handling intervening signals

2010-06-22T09:40:50+00:00

A signal delivered between a hw_breakpoint_handler() and the
single_step_dabr_instruction() will not have the breakpoint active
while the signal handler is running -- the signal delivery will
set up a new MSR value which will not have MSR_SE set, so we
won't get the signal step interrupt until and unless the signal
handler returns (which it may never do).

To fix this, we restore the breakpoint when delivering a signal --
we clear the MSR_SE bit and set the DABR again.  If the signal
handler returns, the DABR interrupt will occur again when the
instruction that we were originally trying to single-step gets
re-executed.

[Paul Mackerras  pointed out the need to do this.]

Signed-off-by: K.Prasad 
Signed-off-by: Paul Mackerras

powerpc/booke: Add support for advanced debug registers

2010-02-17T03:03:17+00:00

powerpc/booke: Add support for advanced debug registers

From: Dave Kleikamp 

Based on patches originally written by Torez Smith.

This patch defines context switch and trap related functionality
for BookE specific Debug Registers. It adds support to ptrace()
for setting and getting BookE related Debug Registers

Signed-off-by: Dave Kleikamp 
Cc: Torez Smith  
Cc: Benjamin Herrenschmidt 
Cc: David Gibson 
Cc: Josh Boyer 
Cc: Kumar Gala 
Cc: Sergio Durigan Junior 
Cc: Thiago Jung Bauermann 
Cc: linuxppc-dev list 
Signed-off-by: Benjamin Herrenschmidt

powerpc/booke: Introduce new CONFIG options for advanced debug registers

2010-02-17T03:03:16+00:00

powerpc/booke: Introduce new CONFIG options for advanced debug registers

From: Dave Kleikamp 

Introduce new config options to simplify the ifdefs pertaining to the
advanced debug registers for booke and 40x processors:

CONFIG_PPC_ADV_DEBUG_REGS - boolean: true for dac-based processors
CONFIG_PPC_ADV_DEBUG_IACS - number of IAC registers
CONFIG_PPC_ADV_DEBUG_DACS - number of DAC registers
CONFIG_PPC_ADV_DEBUG_DVCS - number of DVC registers
CONFIG_PPC_ADV_DEBUG_DAC_RANGE - DAC ranges supported

Beginning conservatively, since I only have the facilities to test 440
hardware.  I believe all 40x and booke platforms support at least 2 IAC
and 2 DAC registers.  For 440, 4 IAC and 2 DVC registers are enabled, as
well as the DAC ranges.

Signed-off-by: Dave Kleikamp 
Acked-by: David Gibson 
Signed-off-by: Benjamin Herrenschmidt

powerpc: Sanitize stack pointer in signal handling code

2009-03-27T05:58:24+00:00

On powerpc64 machines running 32-bit userspace, we can get garbage bits in the
stack pointer passed into the kernel.  Most places handle this correctly, but
the signal handling code uses the passed value directly for allocating signal
stack frames.

This fixes the issue by introducing a get_clean_sp function that returns a
sanitized stack pointer.  For 32-bit tasks on a 64-bit kernel, the stack
pointer is masked correctly.  In all other cases, the stack pointer is simply
returned.

Additionally, we pass an 'is_32' parameter to get_sigframe now in order to
get the properly sanitized stack.  The callers are know to be 32 or 64-bit
statically.

Signed-off-by: Josh Boyer 
Signed-off-by: Benjamin Herrenschmidt

powerpc: Add TIF_NOTIFY_RESUME support for tracehook

2008-07-28T06:30:50+00:00

This adds TIF_NOTIFY_RESUME support for powerpc.  When set,
we call tracehook_notify_resume() on the way to user mode.
This overloads do_signal() to do the work, but changes its
arguments to it has the TIF_* bits handy in a register and
drops the useless first argument that was always zero.

Signed-off-by: Roland McGrath 
Signed-off-by: Benjamin Herrenschmidt

powerpc: Call tracehook_signal_handler() when setting up signal frames

2008-07-28T06:30:49+00:00

This makes the powerpc signal handling code call tracehook_signal_handler()
after a handler is set up.  This means that using PTRACE_SINGLESTEP to
enter a signal handler will report to ptrace on the first instruction of
the handler, instead of the second.  This is consistent with what x86 and
other machines do, and what users and debuggers want.

BenH: Fixed up the test for the trap value.

Signed-off-by: Roland McGrath 
Signed-off-by: Benjamin Herrenschmidt