| /openbmc/docs/designs/ |
| H A D | design-template.md | 8 in a single reasonably small patchset that has little impact to any other
105 API impact? Security impact? Documentation impact? Performance impact? Developer
106 impact? Upgradability impact?
117 How will this be tested? How will this feature impact CI testing?
|
| H A D | phosphor-hwmon-refactoring.md | 69 The refactoring should have no external API impact. Performance impact should be
|
| H A D | psu-monitoring.md | 121 The application is expected to have some impact on the PLDM API, due to the
126 The main documentation impact should be this design document. Future
129 The application is expected to have a similar or lesser performance impact than
|
| H A D | uart-mux-support.md | 73 3. The mux state can always change and has no impact on existing conflicting
139 What should occur? And does this choice impact how we choose to control the mux?
289 system are related, and what the impact might be of activating any one of them.
328 D-Bus representation above, the discussion on the PDI patch, and the impact on
467 ### API Impact
469 ### Performance Impact
473 ### Developer Impact
|
| /openbmc/linux/security/ |
| H A D | Kconfig.hardening | 47 variables initialized), but the performance impact depends
173 impact being driven by the depth of the stack usage, rather than
176 The performance impact on a single CPU system kernel compilation
216 can be useful for estimating the STACKLEAK performance impact for
236 heap content exposures. The performance impact varies by
237 workload, but most cases see <1% impact. Some synthetic
253 The performance impact varies by workload, but is more expensive
255 touching "cold" memory areas. Most cases see 3-5% impact. Some
275 image. This has a less than 1% performance impact on most
324 Enabling this feature will introduce some performance impact,
[all …]
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 98 Redfish. API impact - Add Redfish support for new parameters as well as new user
100 Security impact - update of these parameters should be able to be restricted to
102 Documentation impact - need to document new parameters Performance impact -
106 Developer impact - code to be written by OCC team with guidance from OpenBMC
107 power management team Upgradability impact - None
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-fc_host | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| H A D | sysfs-class-fc_remote_ports | 7 performance impact notification (FPIN) event.
15 performance impact notification (FPIN) event.
23 performance impact notification (FPIN) event.
|
| /openbmc/linux/drivers/zorro/ |
| H A D | zorro.ids | 118 0800 Impact Series I [SCSI Host Adapter and RAM Expansion]
119 2000 Impact Vision 24 [Graphics Card]
132 0100 Impact Series I (4K) [SCSI Host Adapter]
133 0200 Impact Series I (16K/2) [SCSI Host Adapter]
134 0300 Impact Series I (16K/2) [SCSI Host Adapter]
135 0800 Impact 3001 [IDE Interface]
136 0900 Impact 3001 [RAM Expansion]
137 0a00 Impact Series II [RAM Expansion]
152 0d00 Impact 3001 [IDE Interface]
154 2000 Impact Vision 24 [Graphics Card]
[all …]
|
| /openbmc/linux/drivers/atm/ |
| H A D | Kconfig | 60 generally using printks, but still has some impact on performance.
200 When active, these messages can have a significant impact on the
202 inactive, they will have only a modest impact on performance.
247 When active, these messages can have a significant impact on the
249 inactive, they will have only a modest impact on performance.
300 When active, these messages can have a significant impact on
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | NetworkDeviceFunctionMetrics.v1_2_0.json | 127 …"description": "The total number of Congestion Fabric Performance Impact Notifications (FPINs) rec…
137 …"description": "The total number of Delivery Fabric Performance Impact Notifications (FPINs) recei…
157 …"description": "The total number of Link Integrity Fabric Performance Impact Notifications (FPINs)…
167 …"description": "The total number of Peer Congestion Fabric Performance Impact Notifications (FPINs…
187 …"description": "The total number of Congestion Fabric Performance Impact Notifications (FPINs) sen…
197 …"description": "The total number of Delivery Fabric Performance Impact Notifications (FPINs) sent.…
217 …"description": "The total number of Link Integrity Fabric Performance Impact Notifications (FPINs)…
227 …"description": "The total number of Peer Congestion Fabric Performance Impact Notifications (FPINs…
|
| H A D | StorageControllerMetrics.v1_0_3.json | 262 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
263 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
271 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
272 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
280 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
281 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
289 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
290 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
|
| /openbmc/linux/drivers/staging/iio/accel/ |
| H A D | Kconfig | 20 tristate "Analog Devices ADIS16240 Programmable Impact Sensor and Recorder"
26 impact Sensor and recorder.
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/accel/ |
| H A D | adi,adis16240.yaml | 7 title: ADIS16240 Programmable Impact Sensor and Recorder driver
13 ADIS16240 Programmable Impact Sensor and Recorder driver that supports
|
| /openbmc/linux/Documentation/admin-guide/hw-vuln/ |
| H A D | l1tf.rst | 80 impact. The kernel ensures that the address bits of PTEs, which are not
111 deployment scenario. The mitigations, their protection scope and impact
178 data. Flushing the L1D has a performance impact as the processor has to
182 scenarios where guest VMEXIT/VMENTER are rare the performance impact is
279 completely. Disabling SMT can have a significant performance impact, but
280 the impact depends on the hosting scenario and the type of workloads.
281 The impact of disabling SMT needs also to be weighted against the impact
354 significant performance impact especially when the Meltdown mitigation
360 address the performance impact of disabling SMT or EPT.
547 enabled and L1D flushing is not required, but the performance impact is
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | NetworkDeviceFunctionMetrics_v1.xml | 272 …cription" String="The total number of Peer Congestion Fabric Performance Impact Notifications (FPI…
277 …cription" String="The total number of Peer Congestion Fabric Performance Impact Notifications (FPI…
282 …a.Description" String="The total number of Congestion Fabric Performance Impact Notifications (FPI…
287 …a.Description" String="The total number of Congestion Fabric Performance Impact Notifications (FPI…
292 …scription" String="The total number of Link Integrity Fabric Performance Impact Notifications (FPI…
297 …scription" String="The total number of Link Integrity Fabric Performance Impact Notifications (FPI…
302 …ata.Description" String="The total number of Delivery Fabric Performance Impact Notifications (FPI…
307 …ata.Description" String="The total number of Delivery Fabric Performance Impact Notifications (FPI…
|
| H A D | StorageControllerMetrics_v1.xml | 224 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
225 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
229 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
230 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
234 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
235 …erformed vendor-specific thermal-management actions while minimizing the impact on performance in …
239 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
240 …r performed vendor-specific thermal-management actions regardless of the impact on performance in …
|
| /openbmc/openbmc/poky/meta/conf/distro/include/ |
| H A D | cve-extra-exclusions.inc | 65 CVE_STATUS[CVE-2010-4563] = "ignored: cpe:*:linux_kernel:low impact, only enables detection of host…
72 The issue is of low impact, at worst sitting in an infinite loop rather than exploitable."
82 It is a fuzzing related buffer overflow. It is of low impact since most devices \
|
| /openbmc/docs/architecture/ |
| H A D | optionality.md | 38 user-facing impact to function, although might do things like improve
65 impact, and therefore requires an option.
|
| /openbmc/linux/Documentation/accel/qaic/ |
| H A D | qaic.rst | 64 Major number updates indicate changes to the NNC protocol which impact the
67 Minor number updates indicate changes to the NNC protocol which impact the
68 commands (does not impact QAIC).
|
| /openbmc/linux/drivers/cpuidle/governors/ |
| H A D | menu.c | 37 * 2) Performance impact
61 * seconds of idle time. A second independent factor that has big impact on
80 * Limiting Performance Impact
83 * noticeable impact on workloads, which is not acceptable for most sysadmins,
88 * The busier the system, the less impact of C states is acceptable
93 * for selection due to a too high performance impact. So the higher
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-energy.rst | 9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an
11 with a minimal impact on throughput. This document aims at providing an
57 impact.
264 running on a little, but it won't impact the other tasks of the little CPUs
274 impact on throughput for high-utilization scenarios, EAS also implements another
345 EAS uses the EM of a platform to estimate the impact of scheduling decisions on
|
| /openbmc/linux/arch/arm64/kernel/ |
| H A D | Makefile | 18 # can significantly impact performance. Avoid instrumenting the stack trace
19 # collection code to minimize this impact.
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/sensors/phosphor-hwmon/obmc/hwmon/ |
| H A D | iio-hwmon-battery.conf | 8 # Read it every day so it does not impact battery life
|
| /openbmc/openbmc/meta-yadro/meta-nicole/recipes-phosphor/sensors/phosphor-hwmon/obmc/hwmon/ |
| H A D | iio-hwmon-battery.conf | 12 # Read it every day so it does not impact battery life
|