Home
last modified time | relevance | path

Searched full:monitored (Results 1 – 25 of 148) sorted by relevance

123456

/kernel/linux/linux-5.10/Documentation/admin-guide/
Dperf-security.rst11 monitored processes. The data leakage is possible both in scenarios of
32 execution metrics for various monitored parts of the system (e.g.,
95 performance analysis of monitored processes or a system. For example,
177 monitored *scope* is maximized and no perf_events specific limits
184 user or in kernel space can be monitored and captured for later
193 monitored and captured for later analysis. Per-user per-cpu
200 monitored and captured for later analysis. Per-user per-cpu
219 file descriptors that is not less than the number of monitored events
220 multiplied by the number of monitored CPUs.
231 specifically for capturing monitored performance events and related data.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/
Dbq2515x.yaml58 monitored-battery:
60 description: phandle to the battery node being monitored
65 - monitored-battery
85 monitored-battery = <&bat>;
Dbq25980.yaml76 monitored-battery:
78 description: phandle to the battery node being monitored
83 - monitored-battery
110 monitored-battery = <&bat>;
Dingenic,battery.yaml29 monitored-battery:
42 - monitored-battery
60 monitored-battery = <&simple_battery>;
Dcw2015_battery.yaml14 phandle in monitored-battery. If specified the driver uses the
46 monitored-battery:
77 monitored-battery = <&bat>;
Dsc2731_charger.txt9 - monitored-battery: phandle of battery characteristics devicetree node.
38 monitored-battery = <&bat>;
Dbq24190.txt13 - monitored-battery: phandle of battery characteristics devicetree node
48 monitored-battery = <&bat>;
Dbattery.yaml28 The phandle's property should be named "monitored-battery".
161 monitored-battery = <&battery>;
166 monitored-battery = <&battery>;
Dbq27xxx.yaml60 monitored-battery:
92 monitored-battery = <&bat>;
Dsc27xx-fg.txt18 - monitored-battery: Phandle of battery characteristics devicetree node.
56 monitored-battery = <&bat>;
Dsummit,smb347-charger.yaml26 monitored-battery:
143 monitored-battery = <&battery>;
Drohm,bd99954.yaml121 monitored-battery:
155 monitored-battery = <&battery>;
/kernel/linux/linux-5.10/drivers/usb/mon/
Dmon_main.c47 m1->u_bus->monitored = 1; in mon_reader_add()
50 mbus->u_bus->monitored = 1; in mon_reader_add()
177 ubus->monitored = 0; in mon_stop()
185 ubus->monitored = 0; in mon_stop()
202 ubus->monitored = 1; in mon_bus_add()
257 if (ubus->monitored) { in mon_dissolve()
258 ubus->monitored = 0; in mon_dissolve()
/kernel/linux/linux-5.10/Documentation/hwmon/
Dab8500.rst25 temperature are monitored. Other GPADC channels can also be monitored if needed
/kernel/linux/linux-5.10/Documentation/sparc/oradax/
Doracle-dax.rst47 coprocessor. This is done using the monitored load and mwait
168 First, a "monitored load" is achieved via a Load from Alternate Space
170 "monitored wait" is achieved via the mwait instruction (a write to
174 block of data containing the monitored location is modified, then the
188 - go into a loop executing monitored load + monitored wait and
350 /* Monitored Load */
421 /* Monitored Load */
/kernel/linux/linux-5.10/Documentation/accounting/
Dpsi.rst79 /proc/pressure/ representing the resource to be monitored and write the
98 Monitors activate only when system enters stall state for the monitored
100 in the stall state psi signal growth is monitored at a rate of 10 times per
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-devices-edac53 field should be monitored for non-zero values and report
64 field should be also be monitored for non-zero values.
148 to fail. This count field should be monitored for non-zero values
Dsysfs-devices-mapping7 for PCIe root port, which can be monitored by that IIO PMON
/kernel/linux/linux-5.10/fs/lockd/
Dmon.c141 * If this peer is not already monitored, this function sends an
145 * Returns zero if the peer is monitored by the local rpc.statd;
185 * If this peer is monitored, this function sends an upcall to
246 * Construct a unique cookie to match this nsm_handle to this monitored
434 * "mon_name" specifies the host to be monitored.
/kernel/linux/linux-5.10/tools/perf/Documentation/
Dperf-stat.txt123 Do not aggregate counts across all monitored CPUs.
158 container "name" are monitored when they run on the monitored CPUs. Multiple cgroups
281 Aggregate counts per monitored threads, when monitoring threads (-t option)
353 Do not aggregate counts across all monitored CPUs.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/
Dvexpress.txt16 - label : string describing the monitored value
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Duserfaultfd.rst229 When the ``userfaultfd`` is monitored by an external manager, the manager
264 removed, but the area is not, the area remains monitored by the
281 return ``-ENOSPC`` when the monitored process exits at the time of
/kernel/linux/linux-5.10/drivers/vme/
Dvme.c1533 * vme_lm_count - Determine number of VME Addresses monitored
1536 * The number of contiguous addresses monitored is hardware dependent.
1537 * Return the number of contiguous addresses monitored by the
1540 * Return: Count of addresses monitored or -EINVAL when provided with an
1566 * monitored by the location monitor.
1597 * @lm_base: Pointer used to output the base address monitored.
1598 * @aspace: Pointer used to output the address space monitored.
1599 * @cycle: Pointer used to output the VME bus cycle type monitored.
1602 * be monitored by the location monitor.
1638 * monitored addresses. A generic pointer is provided to allow data to be
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra30-actmon.txt6 from the monitored clients.
/kernel/linux/linux-5.10/drivers/powercap/
DKconfig29 and monitored on modern Intel processors (Sandy Bridge and later).

123456