| /openbmc/pldm/libpldmresponder/test/ |
| H A D | libpldmresponder_bios_enum_attribute_test.cpp | 39 "possible_values" : [ "Concurrent", "Disruptive" ], in TEST_F()
40 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
51 ElementsAreArray({"Concurrent", "Disruptive"})); in TEST_F()
56 "possible_value" : [ "Concurrent", "Disruptive" ], in TEST_F()
57 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
96 "possible_values" : [ "Concurrent", "Disruptive" ], in TEST_F()
97 "value_names" : [ "Concurrent", "Disruptive" ], in TEST_F()
98 "default_values" : [ "Disruptive" ], in TEST_F()
126 ON_CALL(biosStringTable, findHandle(StrEq("Disruptive"))) in TEST_F()
136 "possible_values" : [ "Concurrent", "Disruptive" ], in TEST_F()
[all …]
|
| H A D | libpldmresponder_bios_config_test.cpp | 114 "Disruptive", in TEST_F()
|
| H A D | libpldmresponder_systemspecific_bios_test.cpp | 121 "Disruptive", in TEST_F()
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Dump/Entry/ |
| H A D | System.interface.yaml | 27 default: Disruptive
30 impact on the system state. The first type, known as a 'disruptive'
33 requested by a user. Despite its disruptive nature, this dump is able
35 system crashes. The second type is a 'non-disruptive' dump. As the
43 dump request. Non-disruptive dumps consume significant host resources
65 - name: Disruptive
74 non-disruptive system dump request.
85 non-disruptive system dump.
89 start a non-disruptive system dump.
96 requested non-disruptive system dump.
|
| /openbmc/openbmc-test-automation/test_lists/witherspoon/ |
| H A D | regression_bucket_master | 25 # Firmware update(non-disruptive)
56 # Network test cases(non-disruptive)
|
| /openbmc/openpower-debug-collector/dump/ |
| H A D | dump_monitor.cpp | 182 // available assume disruptive. in initiateDumpCollection()
187 System::SystemImpact::Disruptive)) in initiateDumpCollection()
189 lg2::info("Ignoring non-disruptive system dump {PATH}", "PATH", in initiateDumpCollection()
|
| /openbmc/linux/drivers/leds/rgb/ |
| H A D | leds-pwm-multicolor.c | 5 * Copyright 2022 Sven Schwermer <sven.schwermer@disruptive-technologies.com>
187 MODULE_AUTHOR("Sven Schwermer <sven.schwermer@disruptive-technologies.com>");
|
| /openbmc/pldm/libpldmresponder/examples/bios/ |
| H A D | enum_attrs.json | 49 "possible_values": ["Concurrent", "Disruptive"],
|
| /openbmc/linux/Documentation/devicetree/bindings/leds/ |
| H A D | leds-pwm-multicolor.yaml | 10 - Sven Schwermer <sven.schwermer@disruptive-technologies.com>
|
| /openbmc/phosphor-debug-collector/dump-extensions/openpower-dumps/ |
| H A D | dump_manager_resource.cpp | 145 // is provided. The default dump will be a non-disruptive system dump. in createDump()
147 "VSP string is not provided, a non-disruptive system dump will be " in createDump()
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/Dump/Entry/ |
| H A D | Resource.interface.yaml | 26 dump request. Non-disruptive dumps consume significant host resources
|
| /openbmc/pldm/libpldmresponder/test/system_type1/bios_jsons/ |
| H A D | bios_attrs.json | 57 "possible_values": ["Concurrent", "Disruptive"],
|
| /openbmc/pldm/libpldmresponder/test/bios_jsons/ |
| H A D | bios_attrs.json | 57 "possible_values": ["Concurrent", "Disruptive"],
|
| /openbmc/linux/Documentation/driver-api/nvdimm/ |
| H A D | firmware-activate.rst | 11 transactions. However, reboots are disruptive and at least the Intel
|
| /openbmc/linux/drivers/gpu/drm/i915/ |
| H A D | Kconfig.profile | 117 that the reset itself may take longer and so be more disruptive to
|
| /openbmc/linux/include/linux/ |
| H A D | gfp_types.h | 171 * not disruptive and back off even without invoking the OOM killer.
177 * it can sleep). It will avoid disruptive actions like OOM killer. The
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | memory-allocation.rst | 118 and all allocation requests fail early rather than cause disruptive
|
| /openbmc/linux/kernel/rcu/ |
| H A D | Kconfig | 226 grace periods at the expense of being more disruptive.
|
| /openbmc/linux/Documentation/admin-guide/blockdev/ |
| H A D | paride.rst | 198 the parallel port. As the reset operation is potentially disruptive in
|
| /openbmc/linux/drivers/net/ethernet/sfc/siena/ |
| H A D | selftest.c | 708 /* Online (i.e. non-disruptive) testing in efx_siena_selftest()
733 /* Offline (i.e. disruptive) testing in efx_siena_selftest()
|
| /openbmc/linux/drivers/net/ethernet/sfc/falcon/ |
| H A D | selftest.c | 710 /* Online (i.e. non-disruptive) testing in ef4_selftest()
735 /* Offline (i.e. disruptive) testing in ef4_selftest()
|
| /openbmc/linux/drivers/net/ethernet/sfc/ |
| H A D | selftest.c | 703 /* Online (i.e. non-disruptive) testing in efx_selftest()
728 /* Offline (i.e. disruptive) testing in efx_selftest()
|
| /openbmc/linux/drivers/bus/ |
| H A D | arm-cci.c | 244 * disruptive operations. in cci_port_control()
|
| /openbmc/linux/drivers/gpu/drm/i915/gt/uc/ |
| H A D | intel_gsc_fw.c | 435 * Given that an FLR is a very disruptive action (see the FLR function in intel_gsc_uc_fw_upload()
|
| /openbmc/docs/designs/ |
| H A D | bmc-service-failure-debug-and-recovery.md | 102 means, usually by issuing a (disruptive) AC power cycle. On the other hand, if
|