1. 03 3月, 2011 5 次提交
  2. 12 2月, 2011 1 次提交
    • R
      ACPI / ACPICA: Avoid crashing if _PRW is defined for the root object · 2d559513
      Rafael J. Wysocki 提交于
      Some ACPI BIOSes define _PRW for the root object which causes
      acpi_setup_gpe_for_wake() to crash when trying to dereference the
      bogus device_node pointer.  Avoid the crash by checking if
      wake_device is not the root object before attempting to set up the
      "implicit notify" mechanism for it.
      
      The problem was introduced by commit bba63a29
      (ACPICA: Implicit notify support) that added the wake_device argument
      to acpi_setup_gpe_for_wake().
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      2d559513
  3. 19 1月, 2011 5 次提交
  4. 15 1月, 2011 1 次提交
  5. 12 1月, 2011 8 次提交
  6. 07 1月, 2011 1 次提交
    • R
      ACPI / ACPICA: Fix global lock acquisition · 9cd03144
      Rafael J. Wysocki 提交于
      There are two problems with the ACPICA's current implementation of
      the global lock acquisition.  First, acpi_ev_global_lock_handler(),
      which in fact is an interface to the outside of the kernel, doesn't
      validate its input, so it only works correctly if the other side
      (i.e. the ACPI firmware) is fully specification-compliant (as far
      as the global lock is concerned).  Unfortunately, that's known not
      to be the case on some systems (i.e. we get spurious global lock
      signaling interrupts without the pending flag set on some systems).
      Second, acpi_ev_global_lock_handler() attempts to acquire the global
      lock on behalf of a thread waiting for it without checking if there
      actually is such a thread.  Both of these shortcomings need to be
      addressed to prevent all possible race conditions from happening.
      
      Rework acpi_ev_global_lock_handler() so that it doesn't try to
      acquire the global lock and make it signal the availability of the
      global lock to the waiting thread instead.  Make sure that the
      availability of the global lock can only be signaled when there
      is a thread waiting for it and that it can't be signaled more than
      once in a row (to keep acpi_gbl_global_lock_semaphore in balance).
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      9cd03144
  7. 27 12月, 2010 1 次提交
  8. 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
  9. 02 11月, 2010 1 次提交
  10. 23 10月, 2010 1 次提交
  11. 18 10月, 2010 5 次提交
  12. 01 10月, 2010 10 次提交