Searched refs:monitoring (Results 1 – 25 of 257) sorted by relevance
1234567891011
| /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/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/mm/damon/ |
| 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
|
| 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
125 monitoring attributes, ``sampling interval``, ``aggregation interval``,
153 The monitoring overhead of this mechanism will arbitrarily increase as the
[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
|
| /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/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 | 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 …]
|
| 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 …]
|
| /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/Documentation/hwmon/ |
| D | hwmon-kernel-api.rst | 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.
63 monitoring device structure. This function must be called from the driver
[all …]
|
| 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 | 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 | 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 | 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 | 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 | 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/mm/damon/ |
| D | Kconfig | 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.
|
| /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
228 Support performance monitoring as defined in CXL rev 3.0
233 monitoring units and provide standard perf based interfaces.
|
| /Linux-v6.6/net/netlink/ |
| D | Kconfig | 7 tristate "NETLINK: socket monitoring interface"
10 Support for NETLINK socket monitoring interface used by the ss tool.
|
| /Linux-v6.6/sound/pci/mixart/ |
| D | mixart.h | 148 int monitoring; /* pipe used for monitoring issue */ member
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/net/xdp/ |
| D | Kconfig | 11 tristate "XDP sockets: monitoring interface"
15 Support for PF_XDP sockets monitoring interface used by the ss tool.
|
| /Linux-v6.6/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
|
| /Linux-v6.6/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.
|
| /Linux-v6.6/drivers/staging/gdm724x/ |
| D | Kconfig | 12 used for AT commands and DM monitoring applications.
16 GCT-DMx can be used for LTE protocol monitoring
|
1234567891011
