1. 07 Sep, 2005 1 commit
  2. 04 Sep, 2005 3 commits
  3. 01 Sep, 2005 1 commit
    • Nicolas Pitre's avatar
      [ARM] 2865/2: fix fadvise64_64 syscall argument passing · 68d9102f
      Nicolas Pitre authored
      
      
      Patch from Nicolas Pitre
      
      The prototype for sys_fadvise64_64() is:
          long sys_fadvise64_64(int fd, loff_t offset, loff_t len, int advice)
      The argument list is therefore as follows on legacy ABI:
      	fd: type int (r0)
      	offset: type long long (r1-r2)
      	len: type long long (r3-sp[0])
      	advice: type int (sp[4])
      With EABI this becomes:
      	fd: type int (r0)
      	offset: type long long (r2-r3)
      	len: type long long (sp[0]-sp[4])
      	advice: type int (sp[8])
      Not only do we have ABI differences here, but the EABI version requires
      one additional word on the syscall stack.
      To avoid the ABI mismatch and the extra stack space required with EABI
      this syscall is now defined with a different argument ordering
      on ARM as follows:
          long sys_arm_fadvise64_64(int fd, int advice, loff_t offset, loff_t len)
      This gives us the following ABI independent argument distribution:
      	fd: type int (r0)
      	advice: type int (r1)
      	offset: type long long (r2-r3)
      	len: type long long (sp[0]-sp[4])
      Now, since the syscall entry code takes care of 5 registers only by
      default including the store of r4 to the stack, we need a wrapper to
      store r5 to the stack as well.  Because that wrapper was missing and was
      always required this means that sys_fadvise64_64 never worked on ARM and
      therefore we can safely reuse its syscall number for our new
      sys_arm_fadvise64_64 interface.
      Signed-off-by: default avatarNicolas Pitre <nico@cam.org>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      68d9102f
  4. 31 Aug, 2005 1 commit
  5. 29 Aug, 2005 1 commit
    • Steven Rostedt's avatar
      [PATCH] convert signal handling of NODEFER to act like other Unix boxes. · 69be8f18
      Steven Rostedt authored
      
      
      It has been reported that the way Linux handles NODEFER for signals is
      not consistent with the way other Unix boxes handle it.  I've written a
      program to test the behavior of how this flag affects signals and had
      several reports from people who ran this on various Unix boxes,
      confirming that Linux seems to be unique on the way this is handled.
      
      The way NODEFER affects signals on other Unix boxes is as follows:
      
      1) If NODEFER is set, other signals in sa_mask are still blocked.
      
      2) If NODEFER is set and the signal is in sa_mask, then the signal is
      still blocked. (Note: this is the behavior of all tested but Linux _and_
      NetBSD 2.0 *).
      
      The way NODEFER affects signals on Linux:
      
      1) If NODEFER is set, other signals are _not_ blocked regardless of
      sa_mask (Even NetBSD doesn't do this).
      
      2) If NODEFER is set and the signal is in sa_mask, then the signal being
      handled is not blocked.
      
      The patch converts signal handling in all current Linux architectures to
      the way most Unix boxes work.
      
      Unix boxes that were tested:  DU4, AIX 5.2, Irix 6.5, NetBSD 2.0, SFU
      3.5 on WinXP, AIX 5.3, Mac OSX, and of course Linux 2.6.13-rcX.
      
      * NetBSD was the only other Unix to behave like Linux on point #2. The
      main concern was brought up by point #1 which even NetBSD isn't like
      Linux.  So with this patch, we leave NetBSD as the lonely one that
      behaves differently here with #2.
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      69be8f18
  6. 23 Aug, 2005 1 commit
  7. 15 Aug, 2005 1 commit
  8. 10 Aug, 2005 1 commit
  9. 04 Aug, 2005 1 commit
  10. 28 Jul, 2005 1 commit
  11. 26 Jul, 2005 1 commit
  12. 17 Jul, 2005 1 commit
  13. 16 Jul, 2005 1 commit
  14. 11 Jul, 2005 3 commits
  15. 06 Jul, 2005 1 commit
  16. 04 Jul, 2005 1 commit
  17. 01 Jul, 2005 1 commit
  18. 30 Jun, 2005 1 commit
  19. 29 Jun, 2005 2 commits
  20. 28 Jun, 2005 1 commit
  21. 27 Jun, 2005 1 commit
  22. 26 Jun, 2005 1 commit
  23. 25 Jun, 2005 1 commit
    • Russell King's avatar
      [PATCH] ARM: Generic Dynamic Tick Timer support for ARM, take 4 · 8749af68
      Russell King authored
      
      
      This patch adds support for Dynamic Tick Timer for ARM. Dynamic Tick is
      also known as VST (Variable Scheduling Timeouts).
      
      Dynamic Tick has been in use in the OMAP tree since last October.  The
      patch is not intrusive, and does not do anything unless CONFIG_NO_IDLE_HZ
      is defined.  This patch has the following fixed based on comments from
      RMK:
      - Time is updated before calling interrupt handlers.
      - Added new interrupt flag SA_TIMER to avoid duplicate timer interrupts
      - Moved struct dyn_tick_timer to time.h until we at some point probably
        have an arch independent dyn-tick.h
      - Cleaned up testing for DYN_TICK_ENABLED in irq.c
      
       I've cleaned up this patch to fix some remaining issues:
       - Call the timer tick handler with irqs disabled, as it would be from
         a normal interrupt
       - if we have a dyn_tick, we better implement all methods.
       - generic timer_dyn_reprogram() call, to be called before sleeping
       - added command line option - "dyntick=" to allow boot-time control
         of this feature
          -- rmk
      
      Signed-off-by: Tony Lindgren
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      8749af68
  24. 22 Jun, 2005 2 commits
  25. 20 Jun, 2005 2 commits
  26. 19 Jun, 2005 2 commits
  27. 18 Jun, 2005 1 commit
  28. 08 Jun, 2005 1 commit
  29. 31 May, 2005 2 commits
    • Russell King's avatar
      [PATCH] ARM SMP: Fix vector entry · ccea7a19
      Russell King authored
      
      
      The current vector entry system does not allow for SMP.  In
      order to work around this, we need to eliminate our reliance
      on the fixed save areas, which breaks the way we enable
      alignment traps.  This patch changes the way we handle the
      save areas such that we can have one per CPU.
      Signed-off-by: default avatarRussell King <rmk@arm.linux.org.uk>
      ccea7a19
    • Russell King's avatar
      [PATCH] ARM SMP: convert alignment enable · 49f680ea
      Russell King authored
      
      
      The current vector entry system does not allow for SMP.  In
      order to work around this, we need to eliminate our reliance
      on the fixed save areas, which breaks the way we enable
      alignment traps.  This patch makes the alignment trap enable
      code independent of the way we handle the save areas.
      Signed-off-by: default avatarRussell King <rmk@arm.linux.org.uk>
      49f680ea
  30. 21 May, 2005 2 commits