1. 15 8月, 2008 2 次提交
    • I
      x86, nmi: clean UP NMI watchdog failure message · 8bb85190
      Ingo Molnar 提交于
      clean up the failure message - and redirect people to bugzilla
      instead of lkml.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      8bb85190
    • A
      x86, NMI: fix watchdog failure message · 15636668
      Aristeu Rozanski 提交于
      > it just won't work at boot time - the second logic unit will be stuck:
      >
      > Booting processor 1/2 APIC 0x1
      > Initializing CPU#1
      > Calibrating delay using timer specific routine.. 5586.12 BogoMIPS (lpj=2793063)
      > CPU: Trace cache: 12K uops, L1 D cache: 16K
      > CPU: L2 cache: 1024K
      > CPU: Physical Processor ID: 0
      > CPU: Processor Core ID: 1
      > CPU1: Thermal monitoring enabled (TM1)
      >               Intel(R) Pentium(R) D CPU 2.80GHz stepping 04
      > Brought up 2 CPUs
      > testing NMI watchdog ... <4>WARNING: CPU#1: NMI appears to be stuck (0->0)!
      
      while at it... - fix that newline
      Signed-off-by: NAristeu Rozanski <aris@redhat.com>
      Cc: jvillalo@redhat.com
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      15636668
  2. 20 7月, 2008 1 次提交
  3. 18 7月, 2008 1 次提交
    • M
      x86: APIC: remove apic_write_around(); use alternatives · 593f4a78
      Maciej W. Rozycki 提交于
      Use alternatives to select the workaround for the 11AP Pentium erratum
      for the affected steppings on the fly rather than build time.  Remove the
      X86_GOOD_APIC configuration option and replace all the calls to
      apic_write_around() with plain apic_write(), protecting accesses to the
      ESR as appropriate due to the 3AP Pentium erratum.  Remove
      apic_read_around() and all its invocations altogether as not needed.
      Remove apic_write_atomic() and all its implementing backends.  The use of
      ASM_OUTPUT2() is not strictly needed for input constraints, but I have
      used it for readability's sake.
      
      I had the feeling no one else was brave enough to do it, so I went ahead
      and here it is.  Verified by checking the generated assembly and tested
      with both a 32-bit and a 64-bit configuration, also with the 11AP
      "feature" forced on and verified with gdb on /proc/kcore to work as
      expected (as an 11AP machines are quite hard to get hands on these days).
      Some script complained about the use of "volatile", but apic_write() needs
      it for the same reason and is effectively a replacement for writel(), so I
      have disregarded it.
      
      I am not sure what the policy wrt defconfig files is, they are generated
      and there is risk of a conflict resulting from an unrelated change, so I
      have left changes to them out.  The option will get removed from them at
      the next run.
      
      Some testing with machines other than mine will be needed to avoid some
      stupid mistake, but despite its volume, the change is not really that
      intrusive, so I am fairly confident that because it works for me, it will
      everywhere.
      Signed-off-by: NMaciej W. Rozycki <macro@linux-mips.org>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      593f4a78
  4. 12 7月, 2008 1 次提交
  5. 08 7月, 2008 3 次提交
  6. 19 6月, 2008 1 次提交
  7. 12 6月, 2008 1 次提交
  8. 05 6月, 2008 2 次提交
    • M
      x86, nmi: fix build · 75b9f5d2
      mingo@elte.hu 提交于
      fix:
      
      arch/x86/kernel/built-in.o: In function `proc_nmi_enabled':
      : undefined reference to `nmi_watchdog_default'
      arch/x86/kernel/built-in.o: In function `native_smp_prepare_cpus':
      : undefined reference to `nmi_watchdog_default'
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      75b9f5d2
    • C
      x86: nmi - consolidate nmi_watchdog_default for 32bit mode · 3ed3f062
      Cyrill Gorcunov 提交于
      64bit mode bootstrap code does set nmi_watchdog to NMI_NONE
      by default and doing the same on 32bit mode is safe too.
      Such an action saves us from several #ifdef.
      
      Btw, my previous commit
      
      commit 19ec673c
      Author: Cyrill Gorcunov <gorcunov@gmail.com>
      Date:   Wed May 28 23:00:47 2008 +0400
      
          x86: nmi - fix incorrect NMI watchdog used by default
      
      did not fix the problem completely, moreover it
      introduced additional bug - nmi_watchdog would be
      set to either NMI_LOCAL_APIC or NMI_IO_APIC
      _regardless_ to boot option if being enabled thru
      /proc/sys/kernel/nmi_watchdog. Sorry for that.
      Fix it too.
      Signed-off-by: NCyrill Gorcunov <gorcunov@gmail.com>
      Cc: mingo@redhat.com
      Cc: hpa@zytor.com
      Cc: macro@linux-mips.org
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      3ed3f062
  9. 02 6月, 2008 2 次提交
  10. 29 5月, 2008 1 次提交
  11. 26 5月, 2008 8 次提交
  12. 13 5月, 2008 1 次提交
  13. 20 4月, 2008 1 次提交
  14. 17 4月, 2008 4 次提交
  15. 19 2月, 2008 1 次提交
  16. 30 1月, 2008 1 次提交
  17. 25 1月, 2008 1 次提交
  18. 22 1月, 2008 1 次提交
  19. 05 12月, 2007 1 次提交
  20. 27 11月, 2007 1 次提交
  21. 10 11月, 2007 1 次提交
  22. 14 10月, 2007 1 次提交
    • D
      Delete filenames in comments. · 835c34a1
      Dave Jones 提交于
      Since the x86 merge, lots of files that referenced their own filenames
      are no longer correct.  Rather than keep them up to date, just delete
      them, as they add no real value.
      
      Additionally:
      - fix up comment formatting in scx200_32.c
      - Remove a credit from myself in setup_64.c from a time when we had no SCM
      - remove longwinded history from tsc_32.c which can be figured out from
        git.
      Signed-off-by: NDave Jones <davej@redhat.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      835c34a1
  23. 13 10月, 2007 1 次提交
    • T
      x86: Fix irq0 / local apic timer accounting · 3c9aea47
      Thomas Gleixner 提交于
      The clock events merge introduced a change to the nmi watchdog code to
      handle the not longer increasing local apic timer count in the
      broadcast mode. This is fine for UP, but on SMP it pampers over a
      stuck CPU which is not handling the broadcast interrupt due to the
      unconditional sum up of local apic timer count and irq0 count.
      
      To cover all cases we need to keep track on which CPU irq0 is
      handled. In theory this is CPU#0 due to the explicit disabling of irq
      balancing for irq0, but there are systems which ignore this on the
      hardware level. The per cpu irq0 accounting allows us to remove the
      irq0 to CPU0 binding as well.
      
      Add a per cpu counter for irq0 and evaluate this instead of the global
      irq0 count in the nmi watchdog code.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      3c9aea47
  24. 11 10月, 2007 2 次提交