1. 26 Mar, 2008 2 commits
  2. 25 Mar, 2008 1 commit
    • David S. Miller's avatar
      [SPARC64]: Make save_stack_trace() more efficient. · 85a79353
      David S. Miller authored
      Doing a 'flushw' every stack trace capture creates so much overhead
      that it makes lockdep next to unusable.
      
      We only care about the frame pointer chain and the function caller
      program counters, so flush those by hand to the stack frame.
      
      This is significantly more efficient than a 'flushw' because:
      
      1) We only save 16 bytes per active register window to the stack.
      
      2) This doesn't push the entire register window context of the current
         call chain out of the cpu, forcing register window fill traps as we
         return back down.
      
      Note that we can't use 'restore' and 'save' instructions to move
      around the register windows because that wouldn't work on Niagara
      processors.  They optimize 'save' into a new register window by
      simply clearing out the registers instead of pulling them in from
      the on-chip register window backing store.
      
      Based upon a report by Tom Callaway.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      85a79353
  3. 24 Mar, 2008 2 commits
  4. 22 Mar, 2008 1 commit
    • David S. Miller's avatar
      [SPARC64]: Remove most limitations to kernel image size. · 64658743
      David S. Miller authored
      Currently kernel images are limited to 8MB in size, and this causes
      problems especially when enabling features that take up a lot of
      kernel image space such as lockdep.
      
      The code now will align the kernel image size up to 4MB and map that
      many locked TLB entries.  So, the only practical limitation is the
      number of available locked TLB entries which is 16 on Cheetah and 64
      on pre-Cheetah sparc64 cpus.  Niagara cpus don't actually have hw
      locked TLB entry support.  Rather, the hypervisor transparently
      provides support for "locked" TLB entries since it runs with physical
      addressing and does the initial TLB miss processing.
      
      Fully utilizing this change requires some help from SILO, a patch for
      which will be submitted to the maintainer.  Essentially, SILO will
      only currently map up to 8MB for the kernel image and that needs to be
      increased.
      
      Note that neither this patch nor the SILO bits will help with network
      booting.  The openfirmware code will only map up to a certain amount
      of kernel image during a network boot and there isn't much we can to
      about that other than to implemented a layered network booting
      facility.  Solaris has this, and calls it "wanboot" and we may
      implement something similar at some point.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      64658743
  5. 19 Mar, 2008 1 commit
  6. 03 Mar, 2008 3 commits
  7. 29 Feb, 2008 3 commits
  8. 27 Feb, 2008 1 commit
    • David S. Miller's avatar
      [SPARC64]: Loosen checks in exception table handling. · 622eaec6
      David S. Miller authored
      Some parts of the kernel now do things like do *_user() accesses while
      set_fs(KERNEL_DS) that fault on purpose.
      
      See, for example, the code added by changeset
      a0c1e907 ("futex: runtime enable pi
      and robust functionality").
      
      That trips up the ASI sanity checking we make in do_kernel_fault().
      
      Just remove it for now.  Maybe we can add it back later with an added
      conditional which looks at the current get_fs() value.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      622eaec6
  9. 25 Feb, 2008 3 commits
    • Sam Ravnborg's avatar
      [SPARC64]: Fix section mismatch from kernel_map_range · 896aef43
      Sam Ravnborg authored
      Fix following warnings:
      WARNING: vmlinux.o(.text+0x4f980): Section mismatch in reference from the function kernel_map_range() to the function .init.text:__alloc_bootmem()
      WARNING: vmlinux.o(.text+0x4f9cc): Section mismatch in reference from the function kernel_map_range() to the function .init.text:__alloc_bootmem()
      
      alloc_bootmem() is only used during early init and for any subsequent
      call to kernel_map_range() the program logic avoid the call.
      So annotate kernel_map_range() with __ref to tell modpost to
      ignore the reference to a __init function.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      896aef43
    • Sam Ravnborg's avatar
      [SPARC64]: Fix section mismatchs from dr_cpu_data · 7769bd1c
      Sam Ravnborg authored
      Fix following warnings:
      WARNING: vmlinux.o(.text+0x4b258): Section mismatch in reference from the function dr_cpu_data() to the function .devinit.text:mdesc_fill_in_cpu_data()
      WARNING: vmlinux.o(.text+0x4b290): Section mismatch in reference from the function dr_cpu_data() to the function .cpuinit.text:cpu_up()
      
      mdesc_fill_in_cpu_data() is only used during early init and for
      cpu hotplug so the __cpuinit annotation is the correct choice.
      We have the call chain:
      dr_cpu_data() => dr_cpu_configure() => mdesc_fill_in_cpu_data()
      
      dr_cpu_data() is used only during early init and for cpu
      hotplug. So annotating them all __cpuinit solves the
      section mismatch and should be correct.
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      7769bd1c
    • David S. Miller's avatar
      [SPARC]: Fix build in arch/sparc/kernel/led.c · b80a7186
      David S. Miller authored
        CC [M]  arch/sparc/kernel/led.o
      arch/sparc/kernel/led.c: In function 'led_blink':
      arch/sparc/kernel/led.c:35: error: invalid use of undefined type 'struct
      timer_list'
      arch/sparc/kernel/led.c:35: error: 'jiffies' undeclared (first use in
      this function)
      arch/sparc/kernel/led.c:35: error: (Each undeclared identifier is
      reported only once
      arch/sparc/kernel/led.c:35: error: for each function it appears in.)
      arch/sparc/kernel/led.c:36: error: 'avenrun' undeclared (first use in
      this function)
      arch/sparc/kernel/led.c:36: error: 'FSHIFT' undeclared (first use in
      this function)
      arch/sparc/kernel/led.c:36: error: 'HZ' undeclared (first use in this
      function)
      arch/sparc/kernel/led.c:37: error: invalid use of undefined type 'struct
      timer_list'
      arch/sparc/kernel/led.c:39: error: invalid use of undefined type 'struct
      timer_list'
      arch/sparc/kernel/led.c:40: error: invalid use of undefined type 'struct
      timer_list'
      arch/sparc/kernel/led.c:42: error: implicit declaration of function
      'add_timer'
      arch/sparc/kernel/led.c: In function 'led_write_proc':
      arch/sparc/kernel/led.c:70: error: implicit declaration of function
      'copy_from_user'
      arch/sparc/kernel/led.c:84: error: implicit declaration of function
      'del_timer_sync'
      arch/sparc/kernel/led.c: In function 'led_init':
      arch/sparc/kernel/led.c:109: error: implicit declaration of function
      'init_timer'
      arch/sparc/kernel/led.c:110: error: invalid use of undefined type
      'struct timer_list'
      make[1]: *** [arch/sparc/kernel/led.o] Error 1
      
      Based upon original patch by Robert Reif.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b80a7186
  10. 24 Feb, 2008 23 commits