| /Linux-v6.6/drivers/hwmon/pmbus/ |
| 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
91 If you say yes here you get hardware monitoring support for
102 If you say yes here you get hardware monitoring support for the IBM
111 If you say yes here you get hardware monitoring support for Delta
[all …]
|
| /Linux-v6.6/include/linux/ |
| 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 …]
|
| /Linux-v6.6/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 …]
|
| /Linux-v6.6/Documentation/admin-guide/mm/damon/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /Linux-v6.6/Documentation/mm/damon/ |
| 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 …]
|
| 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
|
| /Linux-v6.6/drivers/perf/ |
| 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 …]
|
| /Linux-v6.6/drivers/hwmon/ |
| 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.
189 ADT7410/ADT7420 temperature monitoring chip drivers.
199 ADT7310 and ADT7320 temperature monitoring chips.
210 ADT7410 and ADT7420 temperature monitoring chips.
[all …]
|
| /Linux-v6.6/drivers/platform/x86/siemens/ |
| 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
|
| /Linux-v6.6/mm/damon/ |
| 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.
|
| D | core.c | 63 * damon_register_ops() - Register a monitoring operations set to DAMON.
64 * @ops: monitoring operations set to register.
66 * This function registers a monitoring operations set of valid &struct
90 * damon_select_ops() - Select a monitoring operations to use with the context.
91 * @ctx: monitoring context to use the operations.
92 * @id: id of the registered monitoring operations to select.
94 * This function finds registered monitoring operations set of @id and make
200 * @ranges: array of new monitoring target ranges.
204 * monitoring target to fit in specific ranges.
540 * damon_set_attrs() - Set attributes for the monitoring.
[all …]
|
| /Linux-v6.6/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
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 …]
|
| 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 | 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 | 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
|
| /Linux-v6.6/drivers/platform/x86/intel/pmt/ |
| 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
|
| /Linux-v6.6/drivers/perf/hisilicon/ |
| 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,
|
| /Linux-v6.6/include/rv/ |
| D | da_monitor.h | 75 da_mon->monitoring = 0; \
97 * da_monitor_start_##name - start monitoring \
99 * The monitor will ignore all events until monitoring is set to true. This \
100 * function needs to be called to tell the monitor to start monitoring. \
105 da_mon->monitoring = 1; \
113 return da_mon->monitoring; \
141 /* monitor is actually monitoring */ \
400 * da_handle_start_event_##name - start monitoring or handle event \
403 * to the initial state, so the monitor can start monitoring in the next event. \
429 * da_handle_start_run_event_##name - start monitoring and handle event \
[all …]
|
| /Linux-v6.6/sound/pci/mixart/ |
| D | mixart.h | 148 int monitoring; /* pipe used for monitoring issue */ member
182 int monitoring_active[2]; /* Mixer : Monitoring Active */
183 int monitoring_volume[2]; /* Mixer : Monitoring Volume */
204 …ipe *snd_mixart_add_ref_pipe(struct snd_mixart *chip, int pcm_number, int capture, int monitoring);
205 int snd_mixart_kill_ref_pipe(struct mixart_mgr *mgr, struct mixart_pipe *pipe, int monitoring);
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-damon | 4 Description: Interface for Data Access MONitoring (DAMON). Contains files
53 Description: Reading this file returns the available monitoring operations
59 Description: Writing a keyword for a monitoring operations set ('vaddr' for
60 virtual address spaces monitoring, 'fvaddr' for fixed virtual
61 address ranges monitoring, and 'paddr' for the physical address
62 space monitoring) to this file makes the context to use the
95 monitoring regions of the DAMON context as the value. Reading
102 monitoring regions of the DAMON context as the value. Reading
117 monitoring, respectively.
125 case of the virtual address space monitoring, DAMON
[all …]
|
| /Linux-v6.6/drivers/cxl/ |
| D | Kconfig | 145 tristate "CXL Performance Monitoring Unit"
149 Support performance monitoring as defined in CXL rev 3.0
150 section 13.2: Performance Monitoring. CXL components may have
151 one or more CXL Performance Monitoring Units (CPMUs).
154 monitoring units and provide standard perf based interfaces.
|
| /Linux-v6.6/sound/usb/line6/ |
| D | pcm.h | 46 *) software monitoring (for devices without hardware monitoring)
57 LINE6_STREAM_MONITOR = software monitoring
153 /* Previously captured frame (for software monitoring) */
156 /* Size of previously captured frame (for software monitoring/sync) */
|
