1. 23 3月, 2012 1 次提交
  2. 11 3月, 2012 2 次提交
    • H
      [S390] irq: external interrupt code passing · fde15c3a
      Heiko Carstens 提交于
      The external interrupt handlers have a parameter called ext_int_code.
      Besides the name this paramter does not only contain the ext_int_code
      but in addition also the "cpu address" (POP) which caused the external
      interrupt.
      To make the code a bit more obvious pass a struct instead so the called
      function can easily distinguish between external interrupt code and
      cpu address. The cpu address field however is named "subcode" since
      some external interrupt sources do not pass a cpu address but a
      different parameter (or none at all).
      Signed-off-by: NHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      fde15c3a
    • M
      [S390] rework idle code · 4c1051e3
      Martin Schwidefsky 提交于
      Whenever the cpu loads an enabled wait PSW it will appear as idle to the
      underlying host system. The code in default_idle calls vtime_stop_cpu
      which does the necessary voodoo to get the cpu time accounting right.
      The udelay code just loads an enabled wait PSW. To correct this rework
      the vtime_stop_cpu/vtime_start_cpu logic and move the difficult parts
      to entry[64].S, vtime_stop_cpu can now be called from anywhere and
      vtime_start_cpu is gone. The correction of the cpu time during wakeup
      from an enabled wait PSW is done with a critical section in entry[64].S.
      As vtime_start_cpu is gone, s390_idle_check can be removed as well.
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      4c1051e3
  3. 22 2月, 2012 1 次提交
  4. 30 10月, 2011 3 次提交
  5. 24 7月, 2011 1 次提交
    • J
      [S390] race safe external interrupt registration · 89c9b66b
      Jan Glauber 提交于
      The (un-)register_external_interrupt functions are not race safe if
      more than one interrupt handler is added or deleted for an external
      interrupt concurrently.
      
      Make the registration / unregistration of external interrupts race safe
      by using RCU and a spinlock. RCU is used to avoid a performance penalty
      in the external interrupt handler, the register and unregister functions
      are protected by the spinlock and are not performance critical.
      call_rcu must be used since the SCLP driver uses the interface with
      IRQs disabled. Also use the generic list implementation rather than
      homebrewn list code.
      Signed-off-by: NJan Glauber <jang@linux.vnet.ibm.com>
      Signed-off-by: NMartin Schwidefsky <schwidefsky@de.ibm.com>
      89c9b66b
  6. 26 5月, 2011 1 次提交
  7. 23 5月, 2011 1 次提交
  8. 05 1月, 2011 11 次提交
  9. 11 2月, 2009 1 次提交
  10. 16 10月, 2008 3 次提交
  11. 15 5月, 2008 1 次提交
  12. 29 4月, 2008 1 次提交
  13. 11 10月, 2007 1 次提交
  14. 06 2月, 2007 1 次提交
  15. 04 7月, 2006 2 次提交
  16. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      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