/openbmc/linux/drivers/hwmon/pmbus/ |
H A D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic 33 If you say yes here you get hardware monitoring support for the ACBEL 44 If you say yes here you get hardware monitoring support for Analog 53 If you say yes here you get hardware monitoring support for Analog 63 If you say yes here you get hardware monitoring support for BEL 72 If you say yes here you get hardware monitoring support for BluTek 81 If you say yes here you get hardware monitoring support for the Intel 90 If you say yes here you get hardware monitoring support for 100 If you say yes here you get hardware monitoring support for 111 If you say yes here you get hardware monitoring support for the IBM [all …]
|
/openbmc/linux/include/linux/ |
H A D | damon.h | 39 * struct damon_region - Represents a monitoring target region. 63 * struct damon_target - Represents a monitoring target. 65 * @nr_regions: Number of monitoring target regions of this target. 66 * @regions_list: Head of the monitoring target regions of this target. 69 * Each monitoring context could have multiple targets. For example, a context 72 * virtual address spaces monitoring operations. 82 * enum damos_action - Represents an action of a Data Access Monitoring-based 138 * &weight_nr_accesses, and &weight_age, because monitoring operations are 190 * means DAMON does monitoring and applying the action of the scheme to 230 * @DAMOS_FILTER_TYPE_TARGET: Data Access Monitoring target. [all …]
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | perf-security.rst | 14 depends on the nature of data that perf_events performance monitoring 21 its topology, used kernel and Perf versions, performance monitoring 43 sensitive process data. If PMUs in some monitoring modes capture values 45 to such monitoring modes requires to be ordered and secured properly. 46 So, perf_events performance monitoring and observability operations are 57 monitoring is fully available to privileged processes without access, 71 monitoring and observability operations, thus, bypass *scope* permissions 73 privilege [13]_ (POSIX 1003.1e: 2.2.2.39) for performance monitoring and 75 performance monitoring and observability in the system. 77 For backward compatibility reasons the access to perf_events monitoring and [all …]
|
/openbmc/linux/Documentation/admin-guide/mm/damon/ |
H A D | usage.rst | 108 The monitoring-related information including request specifications and results 145 ``contexts`` directory contains files for controlling the monitoring contexts 153 ``0`` to ``N-1``. Each directory represents each monitoring context. At the 166 DAMON supports multiple types of monitoring operations, including those for 168 available monitoring operations set on the currently running kernel by reading 177 differences between the operations sets in terms of the monitoring target 180 You can set and get what type of monitoring operations DAMON will use for the 189 Files for specifying attributes of the monitoring including required quality 190 and efficiency of the monitoring are in ``monitoring_attrs`` directory. 200 of DAMON's monitoring regions (``min`` and ``max``, respectively), which [all …]
|
H A D | reclaim.rst | 60 no real monitoring and reclamation due to the watermarks-based activation 141 the low watermark, DAMON_RECLAIM becomes active, so starts the monitoring and 157 Sampling interval for the monitoring in microseconds. 159 The sampling interval of DAMON for the cold memory monitoring. Please refer to 165 Aggregation interval for the monitoring in microseconds. 167 The aggregation interval of DAMON for the cold memory monitoring. Please 173 Minimum number of monitoring regions. 175 The minimal number of monitoring regions of DAMON for the cold memory 176 monitoring. This can be used to set lower-bound of the monitoring quality. 177 But, setting this too high could result in increased monitoring overhead. [all …]
|
H A D | lru_sort.rst | 68 no real monitoring and LRU-lists sorting due to the watermarks-based activation 147 the low watermark, DAMON_LRU_SORT becomes active, so starts the monitoring and 162 Sampling interval for the monitoring in microseconds. 164 The sampling interval of DAMON for the cold memory monitoring. Please refer to 170 Aggregation interval for the monitoring in microseconds. 172 The aggregation interval of DAMON for the cold memory monitoring. Please 179 Minimum number of monitoring regions. 181 The minimal number of monitoring regions of DAMON for the cold memory 182 monitoring. This can be used to set lower-bound of the monitoring quality. 183 But, setting this too high could result in increased monitoring overhead. [all …]
|
/openbmc/phosphor-power/phosphor-regulators/docs/ |
H A D | design.md | 19 C++ objects. These objects implement the regulator configuration and monitoring 74 ## Regulator Monitoring 76 ### Enabling Monitoring argument 78 Regulator monitoring is enabled during the system boot after regulators are 86 starts a timer. The timer periodically calls C++ monitoring methods on all the 89 ### Disabling Monitoring argument 91 Regulator monitoring is disabled at the beginning of system shutdown before 101 ### Sensor Monitoring argument 103 When regulator monitoring is enabled, sensor values are read once per second. 122 values are read during monitoring. This can occur in the following cases: [all …]
|
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11" 4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se… 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 11 IMAGE_INSTALL += "power-supplies-monitoring " 21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv… 22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11" 4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se… 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 11 IMAGE_INSTALL += "power-supplies-monitoring " 21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv… 22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
/openbmc/openbmc/meta-hpe/meta-dl385-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 2 SUMMARY = "Power Supplies monitoring for HPE RL300 Gen11" 4 SYSTEMD_SERVICE:${PN} = "psu2-monitoring.service psu1-monitoring.service psu2up.service psu2down.se… 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 11 IMAGE_INSTALL += "power-supplies-monitoring " 21 …install -m 0644 ${UNPACKDIR}/psu2-monitoring.service ${D}${sysconfdir}/system/psu2-monitoring.serv… 22 …install -m 0644 ${UNPACKDIR}/psu1-monitoring.service ${D}${sysconfdir}/system/psu1-monitoring.serv…
|
/openbmc/linux/Documentation/mm/damon/ |
H A D | design.rst | 14 the given monitoring target address-space and available set of 16 - Core: Implements core logics including monitoring overhead/accurach control 25 For data access monitoring and additional low level work, DAMON needs a set of 57 The monitoring operations are defined in two parts: 59 1. Identification of the monitoring target address range for the address space. 69 This is only for the virtual address space monitoring operations 71 manually set the monitoring target address ranges. 78 cases. That said, too huge unmapped areas inside the monitoring target should 121 Monitoring section in Core Logics 125 monitoring attributes, ``sampling interval``, ``aggregation interval``, [all …]
|
H A D | index.rst | 8 monitoring and the monitoring results based system operations. The core 9 monitoring mechanisms of DAMON (refer to :doc:`design` for the detail) make it 11 - *accurate* (the monitoring output is useful enough for DRAM level memory 13 - *light-weight* (the monitoring overhead is low enough to be applied online), 25 (DAMon-based Operation Schemes) in addition to the monitoring. Using the
|
/openbmc/linux/drivers/perf/ |
H A D | Kconfig | 14 Support for PMU events monitoring on the ARM CCI (Cache Coherent 48 Support for PMU events monitoring on the Arm CMN-600 Coherent Mesh 99 Groups (PMCG), which provide monitoring of transactions passing 146 monitoring L2 cache events. 156 monitoring L3 cache events. 187 Support for PMU events monitoring on the ARM DMC-620 memory 208 Support for Driveway PMU events monitoring on Yitian 710 DDR 217 Enable perf support for Marvell DDR Performance monitoring 225 tristate "CXL Performance Monitoring Unit" 228 Support performance monitoring as defined in CXL rev 3.0 [all …]
|
/openbmc/phosphor-power/phosphor-regulators/ |
H A D | README.md | 24 ## Monitoring Voltage Regulators 26 Two types of regulator monitoring are supported: 28 - Sensor monitoring 29 - Phase fault monitoring 31 ### Sensor Monitoring 40 ### Phase Fault Monitoring 55 monitoring.
|
/openbmc/linux/drivers/platform/x86/siemens/ |
H A D | Kconfig | 23 This option enables support for monitoring the voltage of the CMOS 30 tristate "CMOS Battery monitoring for Simatic IPCs based on Apollo Lake GPIO" 35 This option enables CMOS battery monitoring for Simatic Industrial PCs 42 tristate "CMOS Battery monitoring for Simatic IPCs based on Elkhart Lake GPIO" 47 This option enables CMOS battery monitoring for Simatic Industrial PCs 54 tristate "CMOS Battery monitoring for Simatic IPCs based on Nuvoton GPIO" 60 This option enables CMOS battery monitoring for Simatic Industrial PCs
|
/openbmc/linux/mm/damon/ |
H A D | Kconfig | 3 menu "Data Access Monitoring" 6 bool "DAMON: Data Access Monitoring Framework" 28 bool "Data access monitoring operations for virtual address spaces" 32 This builds the default data access monitoring operations for DAMON 36 bool "Data access monitoring operations for the physical address space" 40 This builds the default data access monitoring operations for DAMON 60 the interface for arbitrary data access monitoring. 67 can use the interface for arbitrary data access monitoring.
|
/openbmc/linux/Documentation/hwmon/ |
H A D | hwmon-kernel-api.rst | 1 The Linux Hardware Monitoring kernel API 9 This document describes the API that can be used by hardware monitoring 10 drivers that want to use the hardware monitoring framework. 12 This document does not describe what a hardware monitoring (hwmon) Driver or 14 to communicate with a hardware monitoring device. If you want to know this 22 Each hardware monitoring driver must #include <linux/hwmon.h> and, in some 47 hwmon_device_register_with_info registers a hardware monitoring device. 48 It creates the standard sysfs attributes in the hardware monitoring core, 58 All other hardware monitoring device registration functions are deprecated 61 hwmon_device_unregister deregisters a registered hardware monitoring device. [all …]
|
/openbmc/linux/drivers/hwmon/ |
H A D | Kconfig | 3 # Hardware monitoring chip drivers configuration 7 tristate "Hardware Monitoring support" 11 Hardware monitoring devices let you monitor the hardware health 32 bool "Hardware Monitoring Chip debugging messages" 71 tristate "Ampere's Altra SMpro hardware monitoring driver" 93 AD7414 temperature monitoring chip. 103 AD7416, AD7417 and AD7418 temperature monitoring chips. 190 ADT7410/ADT7420 temperature monitoring chip drivers. 200 ADT7310 and ADT7320 temperature monitoring chips. 211 ADT7410 and ADT7420 temperature monitoring chips. [all …]
|
/openbmc/phosphor-fan-presence/ |
H A D | README.md | 42 - [Fan Monitoring](#fan-monitoring) 48 - [Sensor Monitoring](#sensor-monitoring) 98 - [Fan Monitoring](#fan-monitoring) 101 - [Sensor Monitoring](#sensor-monitoring) - Only supports JSON 165 ### Fan Monitoring 174 Another feature that can be configured is the ability to cancel the monitoring 208 ### Sensor Monitoring 215 monitoring data
|
/openbmc/linux/drivers/platform/x86/intel/pmt/ |
H A D | Kconfig | 3 # Intel Platform Monitoring Technology drivers 9 The Intel Platform Monitoring Technology (PMT) class driver provides 19 tristate "Intel Platform Monitoring Technology (PMT) Telemetry driver" 31 tristate "Intel Platform Monitoring Technology (PMT) Crashlog driver" 35 The Intel Platform Monitoring Technology (PMT) crashlog driver provides
|
/openbmc/phosphor-power/phosphor-regulators/src/ |
H A D | manager.hpp | 74 * Sets whether regulator monitoring is enabled. 76 * When monitoring is enabled: 80 * Regulator monitoring should be enabled when the system is being powered 84 * Regulator monitoring should be disabled when the system is being powered 88 * Regulator monitoring can also be temporarily disabled and then re-enabled 91 * Monitoring should be disabled for only short periods of time; other 94 * @param enable true if monitoring should be enabled, false if it should be 113 * Sensor monitoring timer expired callback function. 217 * Event timer used to initiate sensor monitoring. 222 * Indicates whether regulator monitoring is enabled.
|
H A D | sensors.hpp | 144 * Reading all the sensors once is called a monitoring cycle. The application 146 * each rail. During a monitoring cycle, the following sensor service methods 148 * - startCycle() // At the start of a sensor monitoring cycle 152 * - endCycle() // At the end of a sensor monitoring cycle 182 * Notify the sensors service that the current sensor monitoring cycle has 188 * Notify the sensors service that sensor monitoring has ended for the 215 * Notify the sensors service that a sensor monitoring cycle is starting. 220 * Notify the sensors service that sensor monitoring is starting for the
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-kernel/libpfm/ |
H A D | libpfm4_4.13.0.bb | 1 SUMMARY = "Monitoring tools exploiting the performance monitoring events" 3 monitoring tools exploiting the performance monitoring events such as those \ 4 provided by the Performance Monitoring Unit (PMU) of modern processors."
|
/openbmc/phosphor-power/phosphor-regulators/test/ |
H A D | sensor_monitoring_tests.cpp | 68 * @param monitoring SensorMonitoring object to move into object hierarchy 75 createParentObjects(std::unique_ptr<SensorMonitoring> monitoring) in createParentObjects() argument 80 "vdd", std::move(configuration), std::move(monitoring)); in createParentObjects() 143 SensorMonitoring* monitoring = new SensorMonitoring(std::move(actions)); in TEST() local 147 createParentObjects(std::unique_ptr<SensorMonitoring>{monitoring}); in TEST() 183 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST() 188 monitoring->clearErrorHistory(); in TEST() 198 monitoring->execute(services, *system, *chassis, *device, *rail); in TEST() 219 SensorMonitoring* monitoring = new SensorMonitoring(std::move(actions)); in TEST() local 223 createParentObjects(std::unique_ptr<SensorMonitoring>{monitoring}); in TEST() [all …]
|
/openbmc/linux/drivers/perf/hisilicon/ |
H A D | Kconfig | 13 Provide support for HiSilicon PCIe performance monitoring unit (PMU) 15 Adds the PCIe PMU into perf events system for monitoring latency, 23 Provide support for HNS3 performance monitoring unit (PMU) RCiEP 25 Adds the HNS3 PMU into perf events system for monitoring latency,
|