1. 21 4月, 2014 1 次提交
  2. 11 2月, 2014 1 次提交
  3. 24 9月, 2013 1 次提交
  4. 16 6月, 2013 2 次提交
  5. 25 1月, 2013 1 次提交
  6. 17 7月, 2012 1 次提交
  7. 01 6月, 2012 1 次提交
  8. 22 3月, 2012 2 次提交
  9. 17 1月, 2012 1 次提交
  10. 10 5月, 2011 1 次提交
  11. 25 3月, 2011 1 次提交
  12. 19 1月, 2011 1 次提交
  13. 15 1月, 2011 1 次提交
  14. 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
  15. 01 10月, 2010 1 次提交
  16. 20 4月, 2010 1 次提交
  17. 23 2月, 2010 1 次提交
    • R
      ACPI / ACPICA: Multiple system notify handlers per device · 3f0be671
      Rafael J. Wysocki 提交于
      Currently it only is possible to install one system notify handler
      per namespace node, but this is not enough for PCI run-time power
      management, because we need to install power management notifiers for
      devices that already have hotplug notifiers installed.  While in
      principle this could be handled at the PCI level, that would be
      suboptimal due to the way in which the ACPI-based PCI hotplug code is
      designed.
      
      For this reason, modify ACPICA so that it is possible to install more
      than one system notify handler per namespace node.  Namely, make
      acpi_install_notify_handler(), acpi_remove_notify_handler() and
      acpi_ev_notify_dispatch() use a list of system notify handler objects
      associated with a namespace node.
      
      Make acpi_remove_notify_handler() call acpi_os_wait_events_complete()
      upfront to avoid a situation in which concurrent instance of
      acpi_remove_notify_handler() removes the handler from under us while
      we're waiting for the event queues to flush.
      Signed-off-by: NRafael J. Wysocki <rjw@sisk.pl>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      3f0be671
  18. 23 1月, 2010 1 次提交
  19. 28 3月, 2009 2 次提交
  20. 27 3月, 2009 1 次提交
  21. 09 1月, 2009 2 次提交
  22. 31 12月, 2008 2 次提交
  23. 30 12月, 2008 2 次提交
  24. 17 7月, 2008 1 次提交
  25. 24 4月, 2008 1 次提交
  26. 23 4月, 2008 4 次提交
  27. 10 5月, 2007 3 次提交
  28. 15 3月, 2007 2 次提交