Searched refs:aer (Results 1 – 13 of 13) sorted by relevance
/linux-3.4.99/drivers/pci/pcie/aer/ |
D | aerdrv_errprint.c | 221 struct aer_capability_regs *aer) in cper_print_aer() argument 229 status = aer->cor_status; in cper_print_aer() 230 mask = aer->cor_mask; in cper_print_aer() 234 status = aer->uncor_status; in cper_print_aer() 235 mask = aer->uncor_mask; in cper_print_aer() 249 prefix, aer->uncor_severity); in cper_print_aer() 252 tlp = (const unsigned char *)&aer->header_log; in cper_print_aer()
|
D | Kconfig.debug | 16 help of a user space helper tool aer-inject, which can be 18 http://www.kernel.org/pub/linux/utils/pci/aer-inject/
|
D | Kconfig | 27 source "drivers/pci/pcie/aer/Kconfig.debug"
|
/linux-3.4.99/Documentation/acpi/apei/ |
D | output_format.txt | 96 <aer status string> 98 aer_layer=<aer layer string>, aer_agent=<aer agent string> 108 <aer status string># := 115 <aer status string># := 121 <aer layer string> := 124 <aer agent string> :=
|
/linux-3.4.99/drivers/net/ethernet/ibm/ehea/ |
D | ehea_qmr.c | 231 u64 hret, aer, aerr; in ehea_destroy_cq() local 238 ehea_error_data(cq->adapter, cq->fw_handle, &aer, &aerr); in ehea_destroy_cq() 359 u64 hret, aer, aerr; in ehea_destroy_eq() local 367 ehea_error_data(eq->adapter, eq->fw_handle, &aer, &aerr); in ehea_destroy_eq() 542 u64 hret, aer, aerr; in ehea_destroy_qp() local 550 ehea_error_data(qp->adapter, qp->fw_handle, &aer, &aerr); in ehea_destroy_qp() 1002 u64 *aer, u64 *aerr) in ehea_error_data() argument 1018 *aer = rblock[6]; in ehea_error_data()
|
D | ehea_qmr.h | 396 u64 *aer, u64 *aerr);
|
D | ehea_main.c | 943 u64 resource_type, aer, aerr; in ehea_qp_aff_irq_handler() local 956 &aer, &aerr); in ehea_qp_aff_irq_handler() 959 if ((aer & EHEA_AER_RESET_MASK) || in ehea_qp_aff_irq_handler()
|
/linux-3.4.99/drivers/pci/pcie/ |
D | Makefile | 14 obj-$(CONFIG_PCIEAER) += aer/
|
D | Kconfig | 28 source "drivers/pci/pcie/aer/Kconfig"
|
/linux-3.4.99/Documentation/PCI/ |
D | pcieaer-howto.txt | 139 fatal error happens. The root port aer service driver provides a 195 component has an aer driver. If it has, kernel uses the reset_link 196 callback of the aer driver. If the upstream component has no aer driver 200 they should provide their own aer service drivers with reset_link 265 Then, you need a user space tool named aer-inject, which can be gotten 267 http://www.kernel.org/pub/linux/utils/pci/aer-inject/ 269 More information about aer-inject can be found in the document comes
|
/linux-3.4.99/include/linux/ |
D | aer.h | 53 struct aer_capability_regs *aer);
|
/linux-3.4.99/include/acpi/ |
D | actbl1.h | 553 struct acpi_hest_aer_common aer; member 561 struct acpi_hest_aer_common aer; member 568 struct acpi_hest_aer_common aer; member
|
/linux-3.4.99/arch/x86/kernel/ |
D | pci-calgary_64.c | 543 u32 aer; in calgary_tce_cache_blast() local 550 aer = readl(target); in calgary_tce_cache_blast() 573 writel(aer, target); in calgary_tce_cache_blast()
|