linux-stable.git/arch/sh, branch linux-2.6.33.y

sh: Enable the mmu in start_secondary()

2010-04-26T14:47:47+00:00

commit 4bea3418c737891894b9d3d3e9f8bbd67d66fa38 upstream.

For the boot, enable_mmu() is called from setup_arch() but we don't call
setup_arch() for any of the other cpus. So turn on the non-boot cpu's
mmu inside of start_secondary().

I noticed this bug on an SMP board when trying to map I/O memory
(smsc911x registers) into the kernel address space. Since the Address
Translation bit in MMUCR wasn't set, accessing the virtual address where
the smsc911x registers were supposedly mapped actually performed a
physical address access.

Signed-off-by: Matt Fleming 
Signed-off-by: Paul Mundt 
Signed-off-by: Greg Kroah-Hartman

sh: Fix FDPIC binary loader

2010-04-26T14:47:46+00:00

commit d5ab780305bb6d60a7b5a74f18cf84eb6ad153b1 upstream.

Ensure that the aux table is properly initialized, even when optional
features are missing. Without this, the FDPIC loader did not work.

Signed-off-by: Andrew Stubbs 
Signed-off-by: Paul Mundt 
Signed-off-by: Greg Kroah-Hartman

sh: Fix zImage boot using fixed PMB.

2010-04-01T23:01:20+00:00

commit 319c2cc761505ee54a9536c5d0b9c2ee3fb33866 upstream.

Signed-off-by: Nobuhiro Iwamatsu 
Signed-off-by: Yoshihiro Shimoda 
Signed-off-by: Paul Mundt 
Signed-off-by: Greg Kroah-Hartman

sh64: fix tracing of signals.

2010-02-15T05:17:45+00:00

This follows the parisc change to ensure that tracehook_signal_handler()
is aware of when we are single-stepping in order to ptrace_notify()
appropriately. While this was implemented for 32-bit SH, sh64 neglected
to make use of TIF_SINGLESTEP when it was folded in with the 32-bit code,
resulting in ptrace_notify() never being called.

As sh64 uses all of the other abstractions already, this simply plugs in
the thread flag in the appropriate enable/disable paths and fixes up the
tracehook notification accordingly. With this in place, sh64 is brought
in line with what 32-bit is already doing.

Reported-by: Mike Frysinger 
Signed-off-by: Paul Mundt

sh: Remove superfluous setup_frame_reg call

2010-02-08T01:47:11+00:00

There's no need to setup the frame pointer again in
call_handle_tlbmiss. The frame pointer will already have been setup in
handle_interrupt.

Signed-off-by: Matt Fleming 
Signed-off-by: Paul Mundt

sh: Don't continue unwinding across interrupts

2010-02-08T01:47:04+00:00

Unfortunately, due to poor DWARF info in current toolchains, unwinding
through interrutps cannot be done reliably. The problem is that the
DWARF info for function epilogues is wrong.

Take this standard epilogue sequence,

80003cc4:       e3 6f           mov     r14,r15
80003cc6:       26 4f           lds.l   @r15+,pr
80003cc8:       f6 6e           mov.l   @r15+,r14
						<---- interrupt here
80003cca:       f6 6b           mov.l   @r15+,r11
80003ccc:       f6 6a           mov.l   @r15+,r10
80003cce:       f6 69           mov.l   @r15+,r9
80003cd0:       0b 00           rts

If we take an interrupt at the highlighted point, the DWARF info will
bogusly claim that the return address can be found at some offset from
the frame pointer, even though the frame pointer was just restored. The
worst part is if the unwinder finds a text address at the bogus stack
address - unwinding will continue, for a bit, until it finally comes
across an unexpected address on the stack and blows up.

The only solution is to stop unwinding once we've calculated the
function that was executing when the interrupt occurred. This PC can be
easily calculated from pt_regs->pc.

Signed-off-by: Matt Fleming 
Signed-off-by: Paul Mundt

sh: Setup frame pointer in handle_exception path

2010-02-08T01:46:53+00:00

In order to allow the DWARF unwinder to unwind through exceptions we
need to setup the frame pointer register (r14).

Signed-off-by: Matt Fleming 
Signed-off-by: Paul Mundt

sh: Correct the offset of the return address in ret_from_exception

2010-02-08T01:46:46+00:00

The address that ret_from_exception and ret_from_irq will return to is
found in the stack slot for SPC, not PR. This error was causing the
DWARF unwinder to pick up the wrong return address on the stack and then
unwind using the unwind tables for the wrong function.

While I'm here I might as well add CFI annotations for the other
registers since they could be useful when unwinding.

Signed-off-by: Matt Fleming 
Signed-off-by: Paul Mundt

sh: Fix access to released memory in clk_debugfs_register_one()

2010-02-02T02:32:23+00:00

Signed-off-by: Marek Skuczynski 
Signed-off-by: Paul Mundt

sh: Fix access to released memory in dwarf_unwinder_cleanup()

2010-02-02T02:32:22+00:00

Signed-off-by: Marek Skuczynski 
Acked-by: Matt Fleming 
Signed-off-by: Paul Mundt