1. 27 Jul, 2007 1 commit
    • Heiko Carstens's avatar
      [S390] Fix IRQ tracing. · b771aeac
      Heiko Carstens authored
      
      
      If a machine check is pending and the external or I/O interrupt handler
      returns to userspace io_mcck_pending is going to call s390_handle_mcck.
      Before this happens a call to TRACE_IRQS_ON was already made since we
      know that we are going back to userspace and hence interrupts will be
      enabled. So there was an indication that interrupts are enabled while
      in reality they are still disabled.
      s390_handle_mcck will do a local_irq_save/restore pair and confuse
      lockdep which later complains about inconsistent irq tracing.
      To solve this just call trace_hardirqs_off before calling
      s390_handle_mcck and trace_hardirqs_on afterwards.
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      b771aeac
  2. 10 Jul, 2007 1 commit
  3. 19 Jun, 2007 1 commit
  4. 27 Apr, 2007 1 commit
  5. 28 Sep, 2006 1 commit
  6. 20 Sep, 2006 1 commit
  7. 03 Jul, 2006 1 commit
  8. 01 Jul, 2006 1 commit
  9. 30 Jun, 2006 1 commit
  10. 29 Jun, 2006 2 commits
    • Martin Schwidefsky's avatar
      [S390] remove export of sys_call_table · 8f27766a
      Martin Schwidefsky authored
      
      
      Remove export of the sys_call_table symbol to prevent the misuse of it.
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      8f27766a
    • Martin Schwidefsky's avatar
      [S390] virtual cpu accounting vs. machine checks. · 63b12246
      Martin Schwidefsky authored
      
      
      If a machine checks interrupts the external or the i/o interrupt
      handler before they have completed the cpu time calculations, the
      accounting goes wrong. After the cpu returned from the machine check
      handler to the interrupted interrupt handler, a negative cpu time delta
      can occur.  If the accumulated cpu time in lowcore is small enough
      this value can get negative as well. The next jiffy interrupt will pick
      up that negative value, shift it by 12 and add the now huge positive
      value to the cpu time of the process.
      To solve this the machine check handler is modified not to change any
      of the timestamps in the lowcore if the machine check interrupted kernel
      context.
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      63b12246
  11. 01 Feb, 2006 1 commit
  12. 07 Nov, 2005 1 commit
  13. 17 Sep, 2005 1 commit
  14. 09 Sep, 2005 1 commit
  15. 05 Sep, 2005 1 commit
    • Martin Schwidefsky's avatar
      [PATCH] s390: machine check handler bugs · ae6aa2ea
      Martin Schwidefsky authored
      
      
      The new machine check handler still has a few bugs.
      
      1) The system entry time has to be stored in the machine check handler,
      
      2) the machine check return psw may not be stored at the usual place
         because it might overwrite the return psw of the interrupted context,
      
      3) the return address for the call to s390_handle_mcck in the i/o interrupt
         handler is not correct,
      
      4) the system call cleanup has to take the different save area of the
         machine check handler into account,
      
      5) the machine check handler may not call UPDATE_VTIME before
         CREATE_STACK_FRAME, and
      
      6) the io leave path needs a critical section cleanup to make sure that the
         TIF_MCCK_PENDING bit is really checked before switching back to user space.
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ae6aa2ea
  16. 27 Jul, 2005 1 commit
  17. 25 Jun, 2005 1 commit
  18. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4