1. 28 1月, 2008 23 次提交
  2. 25 1月, 2008 3 次提交
  3. 07 11月, 2007 6 次提交
  4. 02 11月, 2007 2 次提交
    • K
      sh: Terminate .eh_frame in VDSO with a 4-byte 0. · f38c5a69
      Kaz Kojima 提交于
      It's assumed that .eh_frame is terminated with 4-byte 0 in shared
      libraries and executable.  It seems to be the case for VDSOs too.
      Without this terminator, I saw failures when unwinding from VDSO,
      though I don't know how other architectures handle this issue.
      For the normal libs, crtendS.o gives this terminator.  We can use
      such terminating objects.  Or we can add a 4-byte 0 with modifying
      the linker script like as the patch below.
      Signed-off-by: NKaz Kojima <kkojima@rr.iij4u.or.jp>
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      f38c5a69
    • P
      sh: Decouple 4k and soft/hardirq stacks. · 110ed282
      Paul Mundt 提交于
      While using separate IRQ stacks can cut down on stack consumption,
      many users can also use 4k stacks directly without the additional
      need of separate stacks for soft and hardirqs.
      
      With this split, we support the same rationale for 4KSTACKS as
      m68knommu, with the IRQSTACKS abstraction as per ppc64.
      Signed-off-by: NPaul Mundt <lethal@linux-sh.org>
      110ed282
  5. 31 10月, 2007 1 次提交
  6. 30 10月, 2007 5 次提交