1. 18 Nov, 2009 1 commit
  2. 12 Nov, 2009 1 commit
  3. 30 Jun, 2009 1 commit
    • Jan Beulich's avatar
      [IA64] address compiler warnings perfmon.c/salinfo.c · fa276f36
      Jan Beulich authored
      
      
      perfmon.c has a dubious cast directly from "int" to "void *". Add
      an intermediate cast to "long" to keep gcc happy.
      
      salinfo.c uses "down_trylock()" in a highly creative way (explained
      in the comments in the file) ... but it does kick out this warning:
      
       arch/ia64/kernel/salinfo.c:195: warning: ignoring return value of 'down_trylock'
      
      which people occasionally try to "fix" in ways that do not work. Use some
      casts to keep gcc quiet.
      Signed-off-by: default avatarJan Beulich <jbeulich@novell.com>
      Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
      fa276f36
  4. 17 Jun, 2009 2 commits
    • Matthew Wilcox's avatar
      [IA64] Convert ia64 to use int-ll64.h · e088a4ad
      Matthew Wilcox authored
      
      
      It is generally agreed that it would be beneficial for u64 to be an
      unsigned long long on all architectures.  ia64 (in common with several
      other 64-bit architectures) currently uses unsigned long.  Migrating
      piecemeal is too painful; this giant patch fixes all compilation warnings
      and errors that come as a result of switching to use int-ll64.h.
      
      Note that userspace will still see __u64 defined as unsigned long.  This
      is important as it affects C++ name mangling.
      
      [Updated by Tony Luck to change efi.h:efi_freemem_callback_t to use
       u64 for start/end rather than unsigned long]
      Signed-off-by: default avatarMatthew Wilcox <willy@linux.intel.com>
      Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
      e088a4ad
    • Thomas Gleixner's avatar
      remove put_cpu_no_resched() · 8b0b1db0
      Thomas Gleixner authored
      
      
      put_cpu_no_resched() is an optimization of put_cpu() which unfortunately
      can cause high latencies.
      
      The nfs iostats code uses put_cpu_no_resched() in a code sequence where a
      reschedule request caused by an interrupt between the get_cpu() and the
      put_cpu_no_resched() can delay the reschedule for at least HZ.
      
      The other users of put_cpu_no_resched() optimize correctly in interrupt
      code, but there is no real harm in using the put_cpu() function which is
      an alias for preempt_enable().  The extra check of the preemmpt count is
      not as critical as the potential source of missing a reschedule.
      
      Debugged in the preempt-rt tree and verified in mainline.
      
      Impact: remove a high latency source
      
      [akpm@linux-foundation.org: build fix]
      Signed-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: Tony Luck <tony.luck@intel.com>
      Cc: Trond Myklebust <Trond.Myklebust@netapp.com>
      Cc: "J. Bruce Fields" <bfields@fieldses.org>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      8b0b1db0
  5. 27 Mar, 2009 1 commit
  6. 16 Mar, 2009 1 commit
  7. 13 Nov, 2008 2 commits
  8. 01 Nov, 2008 1 commit
    • Al Viro's avatar
      saner FASYNC handling on file close · 233e70f4
      Al Viro authored
      
      
      As it is, all instances of ->release() for files that have ->fasync()
      need to remember to evict file from fasync lists; forgetting that
      creates a hole and we actually have a bunch that *does* forget.
      
      So let's keep our lives simple - let __fput() check FASYNC in
      file->f_flags and call ->fasync() there if it's been set.  And lose that
      crap in ->release() instances - leaving it there is still valid, but we
      don't have to bother anymore.
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      233e70f4
  9. 06 Oct, 2008 1 commit
  10. 26 Jul, 2008 1 commit
  11. 26 Jun, 2008 2 commits
  12. 11 Jun, 2008 1 commit
  13. 14 May, 2008 1 commit
  14. 01 May, 2008 2 commits
  15. 29 Apr, 2008 1 commit
  16. 22 Apr, 2008 1 commit
    • Jeff Garzik's avatar
      [IA64] minor irq handler cleanups · 9010eff0
      Jeff Garzik authored
      
      
      - remove unused 'irq' argument from pfm_do_interrupt_handler()
      
      - remove pointless cast to void*
      
      - add KERN_xxx prefix to printk()
      
      - remove braces around singleton C statement
      
      - in tioce_provider.c, start tioce_dma_consistent() and
        tioce_error_intr_handler() function declarations in column 0
      
      This change's main purpose is to prepare for the patchset in
      jgarzik/misc-2.6.git#irq-remove, that explores removal of the
      never-used 'irq' argument in each interrupt handler.
      Signed-off-by: default avatarJeff Garzik <jgarzik@redhat.com>
      Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
      9010eff0
  17. 09 Apr, 2008 1 commit
  18. 06 Mar, 2008 1 commit
  19. 08 Feb, 2008 1 commit
  20. 05 Feb, 2008 1 commit
  21. 04 Feb, 2008 1 commit
  22. 06 Dec, 2007 1 commit
  23. 06 Nov, 2007 1 commit
    • Tony Luck's avatar
      [IA64] Fix perfmon sysctl directory modes · e3ad42be
      Tony Luck authored
      
      
      New sanity checks in sysctl_check_table() complain about a couple
      of mode 0755 that should be 0555 in the perfmon code:
      
      sysctl table check failed: /kernel .1 Writable sysctl directory
      sysctl table check failed: /kernel/perfmon  Writable sysctl directory
      Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
      e3ad42be
  24. 19 Oct, 2007 1 commit
  25. 12 Oct, 2007 1 commit
  26. 31 Jul, 2007 1 commit
  27. 11 May, 2007 1 commit
  28. 08 May, 2007 1 commit
  29. 06 Mar, 2007 1 commit
    • Nick Piggin's avatar
      [IA64] permon use-after-free fix · 41d5e5d7
      Nick Piggin authored
      
      
      Perfmon associates vmalloc()ed memory with a file descriptor, and installs
      a vma mapping that memory.  Unfortunately, the vm_file field is not filled
      in, so processes with mappings to that memory do not prevent the file from
      being closed and the memory freed.  This results in use-after-free bugs and
      multiple freeing of pages, etc.
      
      I saw this bug on an Altix on SLES9.  Haven't reproduced upstream but it
      looks like the same issue is there.
      Signed-off-by: default avatarNick Piggin <npiggin@suse.de>
      Cc: Stephane Eranian <eranian@hpl.hp.com>
      Signed-off-by: default avatarAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
      41d5e5d7
  30. 17 Feb, 2007 1 commit
  31. 14 Feb, 2007 2 commits
  32. 12 Feb, 2007 1 commit
  33. 11 Feb, 2007 1 commit
  34. 08 Dec, 2006 1 commit
  35. 07 Dec, 2006 1 commit