Searched full:monitoring (Results 1 – 25 of 285) sorted by relevance
12345678910>>...12
| /Documentation/admin-guide/ |
| 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 …]
|
| /Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 162 ``contexts`` directory contains files for controlling the monitoring contexts
172 ``0`` to ``N-1``. Each directory represents each monitoring context (refer to
186 DAMON supports multiple types of :ref:`monitoring operations
189 monitoring operations set on the currently running kernel by reading
195 You can set and get what type of monitoring operations DAMON will use for the
204 Files for specifying attributes of the monitoring including required quality
205 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
215 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
216 controls the monitoring overhead, exist. You can set and get the values by
219 For more details about the intervals and monitoring regions range, please refer
[all …]
|
| D | reclaim.rst | 60 no real monitoring and reclamation due to the watermarks-based activation
168 the low watermark, DAMON_RECLAIM becomes active, so starts the monitoring and
184 Sampling interval for the monitoring in microseconds.
186 The sampling interval of DAMON for the cold memory monitoring. Please refer to
192 Aggregation interval for the monitoring in microseconds.
194 The aggregation interval of DAMON for the cold memory monitoring. Please
200 Minimum number of monitoring regions.
202 The minimal number of monitoring regions of DAMON for the cold memory
203 monitoring. This can be used to set lower-bound of the monitoring quality.
204 But, setting this too high could result in increased monitoring overhead.
[all …]
|
| 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 …]
|
| /Documentation/mm/damon/ |
| D | index.rst | 8 monitoring and the monitoring results based system operations. The core
9 monitoring :ref:`mechanisms <damon_design_monitoring>` of DAMON 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),
26 to the monitoring. Using the feature, DAMON users in both kernel and :doc:`user
|
| D | design.rst | 13 The monitoring-related information including the monitoring request
17 types of monitoring.
29 operations for DAMON that depends on the given monitoring target
31 - :ref:`Core <damon_core_logic>`: Implements core logics including monitoring
46 For data access monitoring and additional low level work, DAMON needs a set of
49 monitoring are address-space dependent.
51 1. Identification of the monitoring target address range for the address space.
57 monitoring accruracy and the overhead.
88 and updates the monitoring target address regions so that entire memory
93 monitoring target address ranges.
[all …]
|
| D | faq.rst | 11 specific monitoring operations including monitoring target regions
25 working set size divided by the page size. Because the monitoring target
|
| /Documentation/hwmon/ |
| 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
45 hwmon_device_register_with_info registers a hardware monitoring device.
46 It creates the standard sysfs attributes in the hardware monitoring core,
56 All other hardware monitoring device registration functions are deprecated
59 hwmon_device_unregister deregisters a registered hardware monitoring device.
[all …]
|
| D | lm63.rst | 47 The LM63 is a digital temperature sensor with integrated fan monitoring
50 The LM63 is basically an LM86 with fan speed monitoring and control
72 Note that the pin used for fan monitoring is shared with an alert out
74 speed monitoring will or will not be possible. The proper chip configuration
77 for fan monitoring and alert out. On the LM64, monitoring is always enabled;
|
| D | emc6w201.rst | 22 "The EMC6W201 is an environmental monitoring device with automatic fan
24 This ACPI compliant device provides hardware monitoring for up to six
35 The driver currently only supports the monitoring of the voltages,
|
| D | pc87360.rst | 44 The National Semiconductor PC87360 Super I/O chip contains monitoring and
46 PC87364 chip has monitoring and PWM control for a third fan.
49 hardware monitoring chipsets, not only controlling and monitoring three fans,
50 but also monitoring eleven voltage inputs and two (PC87365) or up to four
66 Fan Monitoring
123 Temperature Monitoring
149 Voltage Monitoring
185 Monitoring of in9 isn't enabled at lower init levels (<3) because that
197 shouldn't be changed once the monitoring has started, but we ignore that
|
| D | sch5627.rst | 20 SMSC SCH5627 Super I/O chips include complete hardware monitoring
27 The SMSC SCH5627 hardware monitoring part also contains an integrated
32 The hardware monitoring part of the SMSC SCH5627 is accessed by talking
|
| D | smsc47m1.rst | 57 contain monitoring and PWM control circuitry for two fans.
60 monitoring block' in addition to the fan monitoring and control. The
61 hardware monitoring block is not supported by this driver, use the
|
| D | gsc-hwmon.rst | 13 This driver supports hardware monitoring for the temperature sensor,
18 Voltage Monitoring
29 Temperature Monitoring
|
| D | pc87427.rst | 24 monitoring capabilities. It can monitor up to 18 voltages, 8 fans and
35 Fan Monitoring
55 Temperature Monitoring
|
| D | nzxt-smart2.rst | 14 This driver implements monitoring and control of fans plugged into the device.
15 Besides typical speed monitoring and PWM duty cycle control, voltage and current
33 during initialization. Speed, voltage, current monitoring will work even without
46 fan[1-3]_input Fan speed monitoring (in rpm).
|
| D | tps23861.rst | 18 This driver supports hardware monitoring for Texas Instruments TPS23861 PoE PSE.
21 and monitoring capabilities.
25 This driver only supports the Auto mode of operation providing monitoring
|
| D | ltc4282.rst | 27 I2C interface and onboard ADC allows for monitoring of board current, voltage,
29 limiting and supply monitoring for applications from 2.9V to 33V. Dual 12V gate
33 LTC4282 is well suited to high power applications because the precise monitoring
55 in0_enable Enable/Disable VSOURCE monitoring
70 in1_enable Enable/Disable VDD monitoring
|
| D | wm831x.rst | 25 Voltage Monitoring
31 Temperature Monitoring
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-event_source-devices-events | 15 Description: Generic performance monitoring events
17 A collection of performance monitoring events that may be
33 Description: Per-pmu performance monitoring events specific to the running system
37 performance monitoring event supported by the <pmu>. The name
40 As performance monitoring event names are case
|
| D | sysfs-bus-event_source-devices-dfl_fme | 22 0x06 local event id for overall monitoring (portid=0xff).
29 for access to all fme pmu performance monitoring events.
35 Description: Read-only. Attribute group to describe performance monitoring
37 a single performance monitoring event supported by this fme pmu.
41 All supported performance monitoring events are listed below.
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | iio-hwmon.yaml | 13 Bindings for hardware monitoring devices connected to ADC controllers
24 List of phandles to ADC channels to read the monitoring values
|
| /Documentation/devicetree/bindings/mfd/ |
| D | ampere,smpro.yaml | 14 monitoring, error monitoring and other miscellaneous features.
|
| /Documentation/trace/rv/ |
| D | runtime-verification.rst | 18 Moreover, given an efficient monitoring method, it is possible execute an
54 In addition to the verification and monitoring of the system, a monitor can
85 execution, blocking the system during the event monitoring. On the other hand,
173 This is an on/off general switcher for monitoring. It resembles the
176 - Writing "0" stops the monitoring
177 - Writing "1" continues the monitoring
178 - Reading returns the current status of the monitoring
181 monitors monitoring the events received from the system.
|
| /Documentation/power/ |
| D | charger-manager.rst | 8 requires temperature monitoring during suspend-to-RAM state
36 monitoring the battery health and tasks, and user processes that are
63 (in-suspend monitoring), the user should provide charger_global_desc
65 This charger_global_desc data for in-suspend monitoring is global
69 and it will manage in-suspend monitoring for all instances of Charger Manager.
72 properly in order to activate in-suspend monitoring:
107 (in-suspend monitoring) results in "normal".
|
12345678910>>...12