Searched full:monitoring (Results 1 – 25 of 721) sorted by relevance
12345678910>>...29
| /Linux-v5.15/include/linux/ |
| D | damon.h | 29 * struct damon_region - Represents a monitoring target region.
43 * struct damon_target - Represents a monitoring target.
45 * @nr_regions: Number of monitoring target regions of this target.
46 * @regions_list: Head of the monitoring target regions of this target.
49 * Each monitoring context could have multiple targets. For example, a context
52 * example, in the virtual address monitoring context, it could be a pidfd or
65 * struct damon_primitive Monitoring primitives for given use cases.
71 * @reset_aggregated: Reset aggregated accesses monitoring results.
77 * space and usecase via the &damon_ctx.primitive. Then, the monitoring thread
79 * the monitoring, @update after each &damon_ctx.primitive_update_interval, and
[all …]
|
| /Linux-v5.15/drivers/hwmon/pmbus/ |
| D | Kconfig | 21 If you say yes here you get hardware monitoring support for generic
35 If you say yes here you get hardware monitoring support for Analog
44 If you say yes here you get hardware monitoring support for Analog
54 If you say yes here you get hardware monitoring support for BEL
63 If you say yes here you get hardware monitoring support for BluTek
72 If you say yes here you get hardware monitoring support for
83 If you say yes here you get hardware monitoring support for the IBM
92 If you say yes here you get hardware monitoring support for Delta
101 If you say yes here you get hardware monitoring support for the INSPUR
110 If you say yes here you get hardware monitoring support for the
[all …]
|
| /Linux-v5.15/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 13 special cases, though. It supports only virtual address spaces monitoring.
21 monitoring.
45 ``regions update interval``, and min/max number of monitoring target regions by
46 reading from and writing to the ``attrs`` file. To know about the monitoring
60 Some types of address spaces supports multiple monitoring target. For example,
61 the virtual memory address spaces monitoring can have multiple processes as the
62 monitoring targets. Users can set the targets by writing relevant id values of
64 ``target_ids`` file. In case of the virtual address spaces monitoring, the
65 values should be pids of the monitoring target processes. For example, below
66 commands set processes having pids 42 and 4242 as the monitoring targets and
[all …]
|
| /Linux-v5.15/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-v5.15/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 most
53 hwmon_device_register_with_groups registers a hardware monitoring device.
64 This function returns a pointer to the newly created hardware monitoring device
72 to register a hardware monitoring device. It creates the standard sysfs
73 attributes in the hardware monitoring core, letting the driver focus on reading
[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 | sch5627.rst | 20 SMSC SCH5627 Super I/O chips include complete hardware monitoring
23 The SMSC SCH5627 hardware monitoring part also contains an integrated
28 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 | 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 | gsc-hwmon.rst | 13 This driver supports hardware monitoring for the temperature sensor,
18 Voltage Monitoring
29 Temperature Monitoring
|
| /Linux-v5.15/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"
85 AD7414 temperature monitoring chip.
95 AD7416, AD7417 and AD7418 temperature monitoring chips.
179 ADT7410/ADT7420 temperature monitoring chip drivers.
189 ADT7310 and ADT7320 temperature monitoring chips.
200 ADT7410 and ADT7420 temperature monitoring chips.
210 ADT7411 voltage and temperature monitoring chip.
[all …]
|
| /Linux-v5.15/mm/damon/ |
| D | core.c | 180 * damon_set_targets() - Set monitoring targets.
181 * @ctx: monitoring context
213 * damon_set_attrs() - Set attributes for the monitoring.
214 * @ctx: monitoring context
217 * @primitive_upd_int: time interval between monitoring primitive updates
264 /* Returns the size upper limit for each monitoring region */
298 * __damon_start() - Starts monitoring with given context.
299 * @ctx: monitoring context
327 * @ctxs: an array of the pointers for contexts to start monitoring
330 * This function starts a group of monitoring threads for a group of monitoring
[all …]
|
| D | Kconfig | 3 menu "Data Access Monitoring"
6 bool "DAMON: Data Access Monitoring Framework"
28 bool "Data access monitoring primitives for virtual address spaces"
32 This builds the default data access monitoring primitives for DAMON
52 can use the interface for arbitrary data access monitoring.
|
| /Linux-v5.15/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-v5.15/Documentation/vm/damon/ |
| D | design.rst | 10 DAMON provides data access monitoring functionality while making the accuracy
32 The low level primitives for the fundamental access monitoring are defined in
35 1. Identification of the monitoring target address range for the address space.
50 cases. That said, too huge unmapped areas inside the monitoring target should
89 monitoring attributes, ``sampling interval``, ``aggregation interval``,
94 Access Frequency Monitoring
117 The monitoring overhead of this mechanism will arbitrarily increase as the
130 increases the access frequency of the region if so. Therefore, the monitoring
141 Even somehow the initial monitoring target regions are well constructed to
144 monitoring quality. To keep the assumption as much as possible, DAMON
[all …]
|
| D | index.rst | 7 DAMON is a data access monitoring framework subsystem for the Linux kernel.
10 - *accurate* (the monitoring output is useful enough for DRAM level memory
12 - *light-weight* (the monitoring overhead is low enough to be applied online),
19 that incurring high data accesses monitoring overhead could implemented again.
|
| /Linux-v5.15/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
68 Groups (PMCG), which provide monitoring of transactions passing
97 monitoring L2 cache events.
107 monitoring L3 cache events.
137 Support for PMU events monitoring on the ARM DMC-620 memory
|
| /Linux-v5.15/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-v5.15/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) */
|
| /Linux-v5.15/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
|
| /Linux-v5.15/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".
|
| /Linux-v5.15/Documentation/ABI/testing/ |
| 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.
|
| 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
|
| /Linux-v5.15/drivers/platform/mellanox/ |
| D | Kconfig | 34 to system resets operation, system reset causes monitoring and some
60 tristate "Mellanox BlueField Performance Monitoring Counters driver"
66 to performance monitoring counters within various blocks in the
|
12345678910>>...29
