1. 17 9月, 2014 1 次提交
  2. 05 9月, 2014 1 次提交
  3. 31 7月, 2014 1 次提交
  4. 07 6月, 2013 2 次提交
  5. 31 5月, 2013 1 次提交
  6. 04 1月, 2013 1 次提交
  7. 22 7月, 2011 1 次提交
    • H
      PCI: PCIe AER: add aer_recover_queue · 0918472c
      Huang Ying 提交于
      In addition to native PCIe AER, now APEI (ACPI Platform Error
      Interface) GHES (Generic Hardware Error Source) can be used to report
      PCIe AER errors too.  To add support to APEI GHES PCIe AER recovery,
      aer_recover_queue is added to export the recovery function in native
      PCIe AER driver.
      
      Recoverable PCIe AER errors are reported via NMI in APEI GHES.  Then
      APEI GHES uses irq_work to delay the error processing into an IRQ
      handler.  But PCIe AER recovery can be very time-consuming, so
      aer_recover_queue, which can be used in IRQ handler, delays the real
      recovery action into the process context, that is, work queue.
      Signed-off-by: NHuang Ying <ying.huang@intel.com>
      Signed-off-by: NJesse Barnes <jbarnes@virtuousgeek.org>
      0918472c
  8. 22 3月, 2011 1 次提交
    • H
      ACPI, APEI, Add PCIe AER error information printing support · c413d768
      Huang Ying 提交于
      The AER error information printing support is implemented in
      drivers/pci/pcie/aer/aer_print.c.  So some string constants, functions
      and macros definitions can be re-used without being exported.
      
      The original PCIe AER error information printing function is not
      re-used directly because the overall format is quite different.  And
      changing the original printing format may make some original users'
      scripts broken.
      Signed-off-by: NHuang Ying <ying.huang@intel.com>
      CC: Jesse Barnes <jbarnes@virtuousgeek.org>
      CC: Zhang Yanmin <yanmin.zhang@intel.com>
      Signed-off-by: NLen Brown <len.brown@intel.com>
      c413d768
  9. 21 10月, 2008 2 次提交
  10. 21 4月, 2008 1 次提交
  11. 11 9月, 2007 1 次提交
  12. 12 7月, 2007 2 次提交
  13. 27 9月, 2006 1 次提交
    • Z
      PCI-Express AER implemetation: AER core and aerdriver · 6c2b374d
      Zhang, Yanmin 提交于
      Patch 3 implements the core part of PCI-Express AER and aerdrv
      port service driver.
      
      When a root port service device is probed, the aerdrv will call
      request_irq to register irq handler for AER error interrupt.
      
      When a device sends an PCI-Express error message to the root port,
      the root port will trigger an interrupt, by either MSI or IO-APIC,
      then kernel would run the irq handler. The handler collects root
      error status register and schedules a work. The work will call
      the core part to process the error based on its type
      (Correctable/non-fatal/fatal).
      
      As for Correctable errors, the patch chooses to just clear the correctable
      error status register of the device.
      
      As for the non-fatal error, the patch follows generic PCI error handler
      rules to call the error callback functions of the endpoint's driver. If
      the device is a bridge, the patch chooses to broadcast the error to
      downstream devices.
      
      As for the fatal error, the patch resets the pci-express link and
      follows generic PCI error handler rules to call the error callback
      functions of the endpoint's driver. If the device is a bridge, the patch
      chooses to broadcast the error to downstream devices.
      Signed-off-by: NZhang Yanmin <yanmin.zhang@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      6c2b374d