1. 31 3月, 2014 1 次提交
  2. 29 1月, 2014 2 次提交
  3. 18 11月, 2013 1 次提交
    • J
      watchdog: Get rid of MODULE_ALIAS_MISCDEV statements · 487722cf
      Jean Delvare 提交于
      I just can't find any value in MODULE_ALIAS_MISCDEV(WATCHDOG_MINOR)
      and MODULE_ALIAS_MISCDEV(TEMP_MINOR) statements.
      
      Either the device is enumerated and the driver already has a module
      alias (e.g. PCI, USB etc.) that will get the right driver loaded
      automatically.
      
      Or the device is not enumerated and loading its driver will lead to
      more or less intrusive hardware poking. Such hardware poking should be
      limited to a bare minimum, so the user should really decide which
      drivers should be tried and in what order. Trying them all in
      arbitrary order can't do any good.
      
      On top of that, loading that many drivers at once bloats the kernel
      log. Also many drivers will stay loaded afterward, bloating the output
      of "lsmod" and wasting memory. Some modules (cs5535_mfgpt which gets
      loaded as a dependency) can't even be unloaded!
      
      If defining char-major-10-130 is needed then it should happen in
      user-space.
      Signed-off-by: NJean Delvare <jdelvare@suse.de>
      Acked-by: NGuenter Roeck <linux@roeck-us.net>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      Cc: Stephen Warren <swarren@wwwdotorg.org>
      Cc: Mike Frysinger <vapier.adi@gmail.com>
      Cc: Wan ZongShun <mcuos.com@gmail.com>
      Cc: Ben Dooks <ben-linux@fluff.org>
      Cc: Kukjin Kim <kgene.kim@samsung.com>
      Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>
      Cc: Jim Cromie <jim.cromie@gmail.com>
      487722cf
  4. 11 10月, 2013 1 次提交
  5. 12 9月, 2013 1 次提交
  6. 12 7月, 2013 1 次提交
  7. 20 12月, 2012 1 次提交
  8. 29 11月, 2012 3 次提交
  9. 10 9月, 2012 1 次提交
  10. 29 6月, 2012 1 次提交
  11. 23 5月, 2012 1 次提交
  12. 26 4月, 2012 1 次提交
  13. 25 4月, 2012 2 次提交
    • D
      x86/nmi: Add new NMI queues to deal with IO_CHK and SERR · 553222f3
      Don Zickus 提交于
      In discussions with Thomas Mingarelli about hpwdt, he explained
      to me some issues they were some when using their virtual NMI
      button to test the hpwdt driver.
      
      It turns out the virtual NMI button used on HP's machines do no
      send unknown NMIs but instead send IO_CHK NMIs.  The way the
      kernel code is written, the hpwdt driver can not register itself
      against that type of NMI and therefore can not successfully
      capture system information before panic'ing.
      
      To solve this I created two new NMI queues to allow driver to
      register against the IO_CHK and SERR NMIs.  Or in the hpwdt all
      three (if you include unknown NMIs too).
      
      The change is straightforward and just mimics what the unknown
      NMI does.
      Reported-and-tested-by: NThomas Mingarelli <thomas.mingarelli@hp.com>
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Link: http://lkml.kernel.org/r/1333051877-15755-3-git-send-email-dzickus@redhat.comSigned-off-by: NIngo Molnar <mingo@kernel.org>
      553222f3
    • D
      watchdog, hpwdt: Remove priority option for NMI callback · 09ee1014
      Don Zickus 提交于
      The NMI_UNKNOWN bucket only allows for one function to register
      to it. The reason for that is because only functions which can
      not determine if the NMI belongs to them or not should register
      and would like to assume/swallow any NMI they see.
      
      As a result it doesn't make sense to let more than one function
      like this register.  In fact, letting a second function fail
      allows us to know that more than one function is going to
      swallow NMIs on the current system. This is better than silently
      being ignored.
      
      Therefore hpwdt's priority mechanism doesn't make sense any
      more.  They will be always first on the NMI_UNKNOWN queue, if
      they register.
      
      Removing this parameter cleans up the code and simplifies things
      for the next patch which changes how nmis are registered.
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: Thomas Mingarelli <thomas.mingarelli@hp.com>
      Cc: Wim Van Sebroeck <wim@iguana.be>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: Linus Torvalds <torvalds@linux-foundation.org>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Link: http://lkml.kernel.org/r/1333051877-15755-2-git-send-email-dzickus@redhat.comSigned-off-by: NIngo Molnar <mingo@kernel.org>
      09ee1014
  14. 28 3月, 2012 2 次提交
  15. 29 2月, 2012 1 次提交
    • M
      watchdog: hpwdt: clean up set_memory_x call for 32 bit · 97d2a10d
      Maxim Uvarov 提交于
      1. address has to be page aligned.
      2. set_memory_x uses page size argument, not size.
      Bug causes with following commit:
      	commit da28179b4e90dda56912ee825c7eaa62fc103797
      	Author: Mingarelli, Thomas <Thomas.Mingarelli@hp.com>
      	Date:   Mon Nov 7 10:59:00 2011 +0100
      
           watchdog: hpwdt: Changes to handle NX secure bit in 32bit path
      
          commit e67d668e upstream.
      
          This patch makes use of the set_memory_x() kernel API in order
          to make necessary BIOS calls to source NMIs.
      Signed-off-by: NMaxim Uvarov <maxim.uvarov@oracle.com>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      Cc: stable <stable@vger.kernel.org>
      97d2a10d
  16. 26 12月, 2011 1 次提交
    • M
      watchdog: hpwdt: Changes to handle NX secure bit in 32bit path · e67d668e
      Mingarelli, Thomas 提交于
      This patch makes use of the set_memory_x() kernel API in order
      to make necessary BIOS calls to source NMIs.
      
      This is needed for SLES11 SP2 and the latest upstream kernel as it appears
      the NX Execute Disable has grown in its control.
      
      Signed-off by: Thomas Mingarelli <thomas.mingarelli@hp.com>
      Signed-off by: Wim Van Sebroeck <wim@iguana.be>
      Cc: stable@kernel.org
      e67d668e
  17. 10 10月, 2011 2 次提交
  18. 20 9月, 2011 1 次提交
  19. 28 7月, 2011 1 次提交
  20. 16 3月, 2011 1 次提交
  21. 14 3月, 2011 1 次提交
    • A
      watchdog: hpwdt: eliminate section mismatch warning · b77b7088
      Axel Lin 提交于
      hpwdt_init_nmi_decoding() is called in hpwdt_init_one error handling,
      thus remove the  __devexit annotation of hpwdt_exit_nmi_decoding().
      
      This patch fixes below warning:
      
      WARNING: drivers/watchdog/hpwdt.o(.devinit.text+0x36f): Section mismatch in reference from the function hpwdt_init_one() to the function .devexit.text:hpwdt_exit_nmi_decoding()
      The function __devinit hpwdt_init_one() references
      a function __devexit hpwdt_exit_nmi_decoding().
      This is often seen when error handling in the init function
      uses functionality in the exit path.
      The fix is often to remove the __devexit annotation of
      hpwdt_exit_nmi_decoding() so it may be used outside an exit section.
      Signed-off-by: NAxel Lin <axel.lin@gmail.com>
      Acked-by: NThomas Mingarelli <Thomas.Mingarelli@hp.com>
      Signed-off-by: NWim Van Sebroeck <wim@iguana.be>
      b77b7088
  22. 07 1月, 2011 1 次提交
    • D
      x86: Convert some devices to use DIE_NMIUNKNOWN · 673a6092
      Don Zickus 提交于
      They are a handful of places in the code that register a die_notifier
      as a catch all in case no claims the NMI.  Unfortunately, they trigger
      on events like DIE_NMI and DIE_NMI_IPI, which depending on when they
      registered may collide with other handlers that have the ability to
      determine if the NMI is theirs or not.
      
      The function unknown_nmi_error() makes one last effort to walk the
      die_chain when no one else has claimed the NMI before spitting out
      messages that the NMI is unknown.
      
      This is a better spot for these devices to execute any code without
      colliding with the other handlers.
      
      The two drivers modified are only compiled on x86 arches I believe, so
      they shouldn't be affected by other arches that may not have
      DIE_NMIUNKNOWN defined.
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: Russ Anderson <rja@sgi.com>
      Cc: Corey Minyard <minyard@acm.org>
      Cc: openipmi-developer@lists.sourceforge.net
      Cc: dann frazier <dannf@hp.com>
      Signed-off-by: NPeter Zijlstra <a.p.zijlstra@chello.nl>
      LKML-Reference: <1294348732-15030-3-git-send-email-dzickus@redhat.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      673a6092
  23. 23 12月, 2010 1 次提交
    • D
      x86, nmi_watchdog: Remove ARCH_HAS_NMI_WATCHDOG and rely on CONFIG_HARDLOCKUP_DETECTOR · 4a7863cc
      Don Zickus 提交于
      The x86 arch has shifted its use of the nmi_watchdog from a
      local implementation to the global one provide by
      kernel/watchdog.c.  This shift has caused a whole bunch of
      compile problems under different config options.  I attempt to
      simplify things with the patch below.
      
      In order to simplify things, I had to come to terms with the
      meaning of two terms ARCH_HAS_NMI_WATCHDOG and
      CONFIG_HARDLOCKUP_DETECTOR.  Basically they mean the same thing,
      the former on a local level and the latter on a global level.
      
      With the old x86 nmi watchdog gone, there is no need to rely on
      defining the ARCH_HAS_NMI_WATCHDOG variable because it doesn't
      make sense any more.  x86 will now use the global
      implementation.
      
      The changes below do a few things.  First it changes the few
      places that relied on ARCH_HAS_NMI_WATCHDOG to use
      CONFIG_X86_LOCAL_APIC (the former was an alias for the latter
      anyway, so nothing unusual here).  Those pieces of code were
      relying more on local apic functionality the nmi watchdog
      functionality, so the change should make sense.
      
      Second, I removed the x86 implementation of
      touch_nmi_watchdog().  It isn't need now, instead x86 will rely
      on kernel/watchdog.c's implementation.
      
      Third, I removed the #define ARCH_HAS_NMI_WATCHDOG itself from
      x86.  And tweaked the include/linux/nmi.h file to tell users to
      look for an externally defined touch_nmi_watchdog in the case of
      ARCH_HAS_NMI_WATCHDOG _or_ CONFIG_HARDLOCKUP_DETECTOR. This
      changes removes some of the ugliness in that file.
      
      Finally, I added a Kconfig dependency for
      CONFIG_HARDLOCKUP_DETECTOR that said you can't have
      ARCH_HAS_NMI_WATCHDOG _and_ CONFIG_HARDLOCKUP_DETECTOR.  You can
      only have one nmi_watchdog.
      
      Tested with
      ARCH=i386: allnoconfig, defconfig, allyesconfig, (various broken
      configs) ARCH=x86_64: allnoconfig, defconfig, allyesconfig,
      (various broken configs)
      
      Hopefully, after this patch I won't get any more compile broken
      emails. :-)
      
      v3:
        changed a couple of 'linux/nmi.h' -> 'asm/nmi.h' to pick-up correct function
        prototypes when CONFIG_HARDLOCKUP_DETECTOR is not set.
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: Peter Zijlstra <peterz@infradead.org>
      Cc: fweisbec@gmail.com
      LKML-Reference: <1293044403-14117-1-git-send-email-dzickus@redhat.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      4a7863cc
  24. 18 11月, 2010 1 次提交
    • D
      x86, nmi_watchdog: Remove all stub function calls from old nmi_watchdog · 072b198a
      Don Zickus 提交于
      Now that the bulk of the old nmi_watchdog is gone, remove all
      the stub variables and hooks associated with it.
      
      This touches lots of files mainly because of how the io_apic
      nmi_watchdog was implemented.  Now that the io_apic nmi_watchdog
      is forever gone, remove all its fingers.
      
      Most of this code was not being exercised by virtue of
      nmi_watchdog != NMI_IO_APIC, so there shouldn't be anything to
      risky here.
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: fweisbec@gmail.com
      Cc: gorcunov@openvz.org
      LKML-Reference: <1289578944-28564-3-git-send-email-dzickus@redhat.com>
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      072b198a
  25. 14 8月, 2010 10 次提交