1. 23 5月, 2012 1 次提交
  2. 26 4月, 2012 1 次提交
  3. 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
  4. 16 4月, 2012 1 次提交
  5. 29 3月, 2012 2 次提交
  6. 28 3月, 2012 32 次提交
  7. 26 3月, 2012 1 次提交
    • R
      ARM: pxa: use common IOMEM definition · 23019a73
      Rob Herring 提交于
      pxa was missed in the moving of IOMEM to a common definition, so lots of
      IOMEM redefined warnings were introduced. So remove pxa IOMEM definition
      and fix all the fallout.
      Reported-by: NPaul Gortmaker <paul.gortmaker@windriver.com>
      Signed-off-by: NRob Herring <rob.herring@calxeda.com>
      Cc: Eric Miao <eric.y.miao@gmail.com>
      Cc: Russell King <linux@arm.linux.org.uk>
      Cc: Haojian Zhuang <haojian.zhuang@marvell.com>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: Jaroslav Kysela <perex@perex.cz>
      Cc: Takashi Iwai <tiwai@suse.de>
      Cc: rtc-linux@googlegroups.com
      Cc: alsa-devel@alsa-project.org
      23019a73