Searched refs:monitoring (Results 1 – 25 of 219) sorted by relevance
123456789
| /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/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/ |
| 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/vm/damon/ |
| 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.
|
| 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``,
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
160 The monitoring target address range could dynamically changed. For example,
|
| D | faq.rst | 24 monitoring of various address spaces. It is focused on memory management
34 specific low level primitive parts including monitoring target regions
49 working set size divided by the page size. Because the monitoring target
|
| /Linux-v5.15/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 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
82 hwmon_device_unregister deregisters a registered hardware monitoring device.
[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 | 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 | 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 | 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 | sl28cpld.rst | 20 monitoring controller. At the moment this controller supports a single fan
22 hardware monitoring might be supported.
|
| /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/net/netlink/ |
| D | Kconfig | 7 tristate "NETLINK: socket monitoring interface"
10 Support for NETLINK socket monitoring interface used by the ss tool.
|
| /Linux-v5.15/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-v5.15/arch/x86/events/ |
| D | Kconfig | 2 menu "Performance monitoring"
18 monitoring on modern processors.
26 monitoring on modern processors.
|
| /Linux-v5.15/net/xdp/ |
| D | Kconfig | 11 tristate "XDP sockets: monitoring interface"
15 Support for PF_XDP sockets monitoring interface used by the ss tool.
|
| /Linux-v5.15/drivers/staging/gdm724x/ |
| D | Kconfig | 12 used for AT commands and DM monitoring applications.
16 GCT-DMx can be used for LTE protocol monitoring
|
| /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/net/packet/ |
| D | Kconfig | 20 tristate "Packet: sockets monitoring interface"
24 Support for PF_PACKET sockets monitoring interface used by the ss tool.
|
| /Linux-v5.15/net/smc/ |
| D | Kconfig | 15 tristate "SMC: socket monitoring interface"
18 Support for SMC socket monitoring interface used by tools such as
|
| /Linux-v5.15/mm/damon/ |
| D | Kconfig | 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/hwmon/ |
| D | Kconfig | 3 # Hardware monitoring chip drivers configuration
11 Hardware monitoring devices let you monitor the hardware health
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.
220 ADT7462 temperature monitoring chips.
230 ADT7470 temperature monitoring chips.
[all …]
|
123456789
