Home
last modified time | relevance | path

Searched refs:monitoring (Results 1 – 25 of 283) sorted by relevance

12345678910>>...12

/linux-6.3-rc2/drivers/hwmon/pmbus/
A DKconfig21 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
82 If you say yes here you get hardware monitoring support for
102 If you say yes here you get hardware monitoring support for Delta
120 If you say yes here you get hardware monitoring support for the
153 If you say yes here you get hardware monitoring support for the
[all …]
/linux-6.3-rc2/Documentation/admin-guide/
A Dperf-security.rst14 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,
75 performance monitoring and observability in the system.
89 [7]_ , whose outcome determines whether monitoring is permitted.
247 *scope* includes per-process performance monitoring only and
272 system, this limit can be easily hit preventing required monitoring
[all …]
/linux-6.3-rc2/Documentation/mm/damon/
A Dindex.rst8 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
A Ddesign.rst10 DAMON provides data access monitoring functionality while making the accuracy
17 level primitives implementations monitoring operations.
21 monitoring operations. If appropriate one is not provided, users can implement
33 The monitoring operations are defined in two parts:
35 1. Identification of the monitoring target address range for the address space.
45 This is only for the virtual address space monitoring operations
47 manually set the monitoring target address ranges.
97 monitoring attributes, ``sampling interval``, ``aggregation interval``,
125 The monitoring overhead of this mechanism will arbitrarily increase as the
149 Even somehow the initial monitoring target regions are well constructed to
[all …]
A Dfaq.rst24 monitoring of various address spaces. It is focused on memory management
34 specific monitoring operations including monitoring target regions
48 working set size divided by the page size. Because the monitoring target
/linux-6.3-rc2/drivers/perf/hisilicon/
A DKconfig13 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-6.3-rc2/Documentation/admin-guide/mm/damon/
A Dusage.rst14 virtual and physical address spaces monitoring. For more detail, please
26 monitoring results. For detailed monitoring results, DAMON provides a
178 differences between the operations sets in terms of the monitoring target
191 and efficiency of the monitoring are in ``monitoring_attrs`` directory.
201 of DAMON's monitoring regions (``min`` and ``max``, respectively), which
213 to ``N-1``. Each directory represents each monitoring target.
513 ``update interval``, and min/max number of monitoring target regions by
552 Note that setting the target ids doesn't start the monitoring.
568 monitoring target regions by themselves.
754 monitoring is turned off, reading the file returns ``none``. ::
[all …]
A Dlru_sort.rst68 no real monitoring and LRU-lists sorting due to the watermarks-based activation
162 Sampling interval for the monitoring in microseconds.
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.
190 Maximum number of monitoring regions.
192 The maximum number of monitoring regions of DAMON for the cold memory
[all …]
A Dreclaim.rst60 no real monitoring and reclamation due to the watermarks-based activation
157 Sampling interval for the monitoring in microseconds.
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.
183 Maximum number of monitoring regions.
185 The maximum number of monitoring regions of DAMON for the cold memory
[all …]
/linux-6.3-rc2/Documentation/hwmon/
A Dhwmon-kernel-api.rst9 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
89 remove function if the hardware monitoring device was registered with
182 The hardware monitoring sensor type.
311 Pointer to the hardware monitoring device.
334 Pointer to the hardware monitoring device.
354 If the hardware monitoring device is registered with
[all …]
A Dtps23861.rst18 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
A Dlm63.rst47 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;
A Dsch5627.rst20 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
A Demc6w201.rst22 "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,
A Dnzxt-smart2.rst14 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).
A Dsmsc47m1.rst57 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-6.3-rc2/mm/damon/
A DKconfig28 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-6.3-rc2/net/netlink/
A DKconfig7 tristate "NETLINK: socket monitoring interface"
10 Support for NETLINK socket monitoring interface used by the ss tool.
/linux-6.3-rc2/drivers/perf/
A DKconfig14 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
128 monitoring L2 cache events.
138 monitoring L3 cache events.
169 Support for PMU events monitoring on the ARM DMC-620 memory
190 Support for Driveway PMU events monitoring on Yitian 710 DDR
199 Enable perf support for Marvell DDR Performance monitoring
/linux-6.3-rc2/sound/pci/mixart/
A Dmixart.h148 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-6.3-rc2/net/xdp/
A DKconfig11 tristate "XDP sockets: monitoring interface"
15 Support for PF_XDP sockets monitoring interface used by the ss tool.
/linux-6.3-rc2/arch/x86/events/
A DKconfig2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
/linux-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-bus-event_source-devices-dfl_fme22 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-6.3-rc2/drivers/staging/gdm724x/
A DKconfig12 used for AT commands and DM monitoring applications.
16 GCT-DMx can be used for LTE protocol monitoring
/linux-6.3-rc2/Documentation/devicetree/bindings/mfd/
A Dampere,smpro.yaml14 monitoring, error monitoring and other miscellaneous features.

Completed in 37 milliseconds

12345678910>>...12