/openbmc/linux/Documentation/gpu/amdgpu/ |
H A D | ras.rst | 2 AMDGPU RAS Support 5 The AMDGPU RAS interfaces are exposed via sysfs (for informational queries) and 8 RAS debugfs/sysfs Control and Error Injection Interfaces 12 :doc: AMDGPU RAS debugfs control interface 14 RAS Reboot Behavior for Unrecoverable Errors 18 :doc: AMDGPU RAS Reboot Behavior for Unrecoverable Errors 20 RAS Error Count sysfs Interface 24 :doc: AMDGPU RAS sysfs Error Count Interface 26 RAS EEPROM debugfs Interface 30 :doc: AMDGPU RAS debugfs EEPROM table reset interface [all …]
|
/openbmc/linux/drivers/ras/ |
H A D | Kconfig | 2 menuconfig RAS config 3 bool "Reliability, Availability and Serviceability (RAS) features" 5 Reliability, availability and serviceability (RAS) is a computer 7 of RAS have a multitude of features that protect data integrity 32 if RAS
|
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-support/rasdaemon/files/ |
H A D | rasdaemon.service | 2 Description=RAS daemon to log the RAS events
|
/openbmc/openpower-hw-diags/analyzer/ras-data/ |
H A D | meson.build | 2 # Install the RAS data files 14 # Install the RAS data schema
|
H A D | ras-data-definition.md | 1 # RAS Data File definition 6 signature. The RAS Data files are used to define, in a data driven fashion, the 7 appropriate RAS actions that should be taken for the root cause signature. 9 The RAS Data will be defined in the JSON data format. Each file will contain a 10 single JSON object (with nested values) which will define the RAS actions for a 21 A new version number should be used for each new RAS data file format so that 69 RAS actions, to be performed in order, with the format: 221 Some RAS actions require additional support that cannot be defined easily in 261 from this chip requiring RAS actions. Each element of this object will have the
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-platform-devices-ampere-smpro | 17 …| 04 | Error status | 4 | See ARM RAS specification for details … 19 …| 08 | Error Address | 8 | See ARM RAS specification for details … 21 …| 16 | Error Misc 0 | 8 | See ARM RAS specification for details … 23 …| 24 | Error Misc 1 | 8 | See ARM RAS specification for details … 25 …| 32 | Error Misc 2 | 8 | See ARM RAS specification for details … 27 …| 40 | Error Misc 3 | 8 | See ARM RAS specification for details … 175 Altra Family RAS Supplement`. 234 For details, see section `5.10 RAS Internal Error Register Definitions,
|
/openbmc/openbmc-test-automation/test_lists/ |
H A D | skip_test_witherspoon | 12 # NXDMAENG UE error injection is not available in RAS specification. 57 # Skipping RAS test cases
|
/openbmc/linux/drivers/platform/x86/intel/ifs/ |
H A D | Kconfig | 8 operation beyond baseline RAS capabilities. To compile this
|
/openbmc/linux/Documentation/networking/device_drivers/ethernet/marvell/ |
H A D | octeontx2.rst | 180 3. RAS events 182 - RAS Error Reporting for NPA_AQ_INST_S/NPA_AQ_RES_S. 240 3. RAS events 242 - RAS Error Reporting for NIX Receive Multicast/Mirror Entry Structure. 243 - RAS Error Reporting for WQE/Packet Data read from Multicast/Mirror Buffer.. 244 - RAS Error Reporting for NIX_AQ_INST_S/NIX_AQ_RES_S.
|
/openbmc/openpower-hw-diags/analyzer/ |
H A D | meson.build | 39 # Install the RAS data files.
|
/openbmc/openbmc-test-automation/docs/ |
H A D | openbmc_test_architecture.md | 47 | BMC/Host reset | | System Functionality | | System RAS |
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/mcelog/ |
H A D | mce-test_git.bb | 7 testing the Linux RAS related features, including CPU/Memory error \
|
/openbmc/linux/Documentation/accel/qaic/ |
H A D | aic100.rst | 215 | | | | Accessibility, Serviceability (RAS) | 492 Reliability, Accessibility, Serviceability (RAS) 495 AIC100 is expected to be deployed in server systems where RAS ideology is 496 applied. Simply put, RAS is the concept of detecting, classifying, and 498 into RAS, AER does not allow for a device to report details about internal 499 errors. Therefore, AIC100 implements a custom RAS mechanism. When a RAS event 502 additional service based on RAS reports.
|
/openbmc/qemu/docs/system/arm/ |
H A D | emulation.rst | 117 - FEAT_RASv1p1 (RAS Extension v1.1) 190 - RAS (Reliability, Serviceability and Availability): "minimum RAS Extension" only
|
/openbmc/u-boot/doc/ |
H A D | README.N1213 | 12 - Return address stack (RAS).
|
/openbmc/docs/designs/ |
H A D | cper-records.md | 18 several architecture definitions for BMC, including section C.2.2 RAS IPMI 19 Message Format, and IPMI based RAS Event Receiver.
|
/openbmc/openbmc/meta-openembedded/meta-oe/dynamic-layers/perl-layer/recipes-support/rasdaemon/ |
H A D | rasdaemon_0.8.3.bb | 1 …rovide a way to get Platform Reliability, Availability and Serviceability (RAS) reports made via t…
|
/openbmc/linux/arch/arm64/kvm/ |
H A D | nested.c | 57 NV_FTR(PFR0, RAS) | in access_nested_id_reg()
|
/openbmc/linux/drivers/acpi/apei/ |
H A D | Kconfig | 62 APEI and some other RAS features.
|
/openbmc/linux/Documentation/arch/arm64/ |
H A D | acpi_object_usage.rst | 35 compliant with the Arm RAS architecture. 55 Must be supplied if RAS support is provided by the platform. It 150 On a platform supports RAS, this table must be supplied if it is not 212 Must be supplied if RAS support is provided by the platform. It 356 **RAS Features 2 table** 358 This table provides interfaces for the RAS capabilities implemented in 363 **RAS Feature table**
|
/openbmc/linux/arch/powerpc/platforms/cell/ |
H A D | Kconfig | 61 bool "RAS features for bare metal Cell BE"
|
/openbmc/qemu/target/arm/ |
H A D | cpu-features.h | 138 return FIELD_EX32(id->id_pfr0, ID_PFR0, RAS) != 0; in isar_feature_aa32_ras() 634 return FIELD_EX64(id->id_aa64pfr0, ID_AA64PFR0, RAS) != 0; in isar_feature_aa64_ras() 639 return FIELD_EX64(id->id_aa64pfr0, ID_AA64PFR0, RAS) >= 2; in isar_feature_aa64_doublefault()
|
/openbmc/qemu/include/hw/cxl/ |
H A D | cxl_component.h | 54 CXLx_CAPABILITY_HEADER(RAS, 0x4)
|
/openbmc/linux/drivers/pci/pcie/ |
H A D | Kconfig | 31 select RAS
|
/openbmc/qemu/hw/cxl/ |
H A D | cxl-component-utils.c | 342 init_cap_reg(RAS, 2, CXL_RAS_CAPABILITY_VERSION); in cxl_component_register_init_common()
|