| /Linux-v5.15/tools/testing/selftests/bpf/verifier/ |
| D | ref_tracking.c | 2 "reference tracking: leak potential reference",
13 "reference tracking: leak potential reference to sock_common",
24 "reference tracking: leak potential reference on stack",
38 "reference tracking: leak potential reference on stack 2",
53 "reference tracking: zero potential reference",
64 "reference tracking: zero potential reference to sock_common",
75 "reference tracking: copy and zero potential references",
88 "reference tracking: release reference without check",
102 "reference tracking: release reference to sock_common without check",
116 "reference tracking: release reference",
[all …]
|
| /Linux-v5.15/net/netfilter/ |
| D | Kconfig | 69 tristate "Netfilter connection tracking support"
74 Connection tracking keeps a record of what packets have passed
101 bool 'Connection mark tracking support'
110 bool 'Connection tracking security mark support'
123 bool 'Connection tracking zones'
126 This option enables support for connection tracking zones.
128 identity. Connection tracking zones allow to have multiple
145 bool "Connection tracking events"
148 If this option is enabled, the connection tracking code will
150 to get notified about changes in the connection tracking state.
[all …]
|
| /Linux-v5.15/Documentation/networking/ |
| D | nf_conntrack-sysctl.rst | 14 Enable connection tracking flow accounting. 64-bit byte and packet
30 considered for connection tracking.
39 If this option is enabled, the connection tracking code will
40 provide userspace with connection tracking events via ctnetlink.
102 Maximum number of allowed connection tracking entries. This value is set
104 Note that connection tracking entries are added to the table twice -- once
170 Enable connection tracking flow timestamping.
|
| D | tipc.rst | 38 - Service Tracking
41 Tracking mechanism to subscribe for binding and unbinding/close events for
44 The service tracking mechanism can also be used for Cluster Topology Tracking,
47 Likewise, the service tracking mechanism can be used for Cluster Connectivity
48 Tracking, i.e., subscribing for up/down events for individual links between
|
| /Linux-v5.15/kernel/time/ |
| D | Kconfig | 144 bool "Force context tracking"
149 support the context tracking subsystem. But there are also
154 context tracking backend but doesn't yet fulfill all the
157 for context tracking and the subsystems that rely on it: RCU
160 dynticks subsystem by forcing the context tracking on all
164 architecture backend for the context tracking.
|
| /Linux-v5.15/drivers/staging/rtl8723bs/hal/ |
| D | HalPhyRf.c | 43 /* Initial Mix mode power tracking */ in ODM_ClearTxPowerTrackingState()
162 /* Record delta swing for mix mode power tracking */ in ODM_TXPowerTrackingCallback_ThermalMeter()
172 /* Record delta swing for mix mode power tracking */ in ODM_TXPowerTrackingCallback_ThermalMeter()
183 /* Record delta swing for mix mode power tracking */ in ODM_TXPowerTrackingCallback_ThermalMeter()
193 /* Record delta swing for mix mode power tracking */ in ODM_TXPowerTrackingCallback_ThermalMeter()
206 …RFCalibrateInfo.DeltaPowerIndexLast[p]; /* Power Index Diff between 2 times Power Tracking */ in ODM_TXPowerTrackingCallback_ThermalMeter()
248 …ibrateInfo.bTxPowerChanged = true; /* Always true after Tx Power is adjusted by power tracking. */ in ODM_TXPowerTrackingCallback_ThermalMeter()
253 /* 2012/04/25 MH Add for tx power tracking to set tx power in tx agc for 88E. */ in ODM_TXPowerTrackingCallback_ThermalMeter()
263 /* Record last time Power Tracking result as base. */ in ODM_TXPowerTrackingCallback_ThermalMeter()
268 /* Record last Power Tracking Thermal Value */ in ODM_TXPowerTrackingCallback_ThermalMeter()
|
| /Linux-v5.15/drivers/soc/aspeed/ |
| D | aspeed-p2a-ctrl.c | 64 struct mutex tracking; member
155 mutex_lock(&ctrl->tracking); in aspeed_p2a_region_acquire()
157 mutex_unlock(&ctrl->tracking); in aspeed_p2a_region_acquire()
191 mutex_lock(&ctrl->tracking); in aspeed_p2a_ioctl()
193 mutex_unlock(&ctrl->tracking); in aspeed_p2a_ioctl()
231 * flipped, and bridge enabled). Either way, this tracking is used, s.t. when
273 mutex_lock(&priv->parent->tracking); in aspeed_p2a_release()
290 /* Note, if another user is trying to ioctl, they can't grab tracking, in aspeed_p2a_release()
292 * If another user is trying to close, they can't grab tracking either. in aspeed_p2a_release()
302 mutex_unlock(&priv->parent->tracking); in aspeed_p2a_release()
[all …]
|
| /Linux-v5.15/drivers/gpu/drm/vmwgfx/ |
| D | vmwgfx_page_dirty.c | 30 * Different methods for tracking dirty:
81 * dirty-tracking method.
113 * vmw_bo_dirty_scan_mkwrite - Reset the mkwrite dirty-tracking method
119 * This function may change the dirty-tracking method.
160 * tracking structure
163 * This function may change the dirty tracking method.
223 * vmw_bo_dirty_add - Add a dirty-tracking user to a buffer object
226 * This function registers a dirty-tracking user to a buffer object.
293 * vmw_bo_dirty_release - Release a dirty-tracking user from a buffer object
296 * This function releases a dirty-tracking user from a buffer object.
[all …]
|
| /Linux-v5.15/tools/perf/tests/ |
| D | switch-tracking.c | 317 * test__switch_tracking - test using sched_switch and tracking events.
320 * tracking events can be recorded for a workload (current process) using the
321 * evsel->core.system_wide and evsel->tracking flags (respectively) with other events
447 /* Check tracking event is tracking */ in test__switch_tracking()
449 pr_debug("Tracking event not tracking\n"); in test__switch_tracking()
453 /* Check non-tracking events are not tracking */ in test__switch_tracking()
457 pr_debug("Non-tracking event is tracking\n"); in test__switch_tracking()
553 /* Check all 4 comm events were seen i.e. that evsel->tracking works */ in test__switch_tracking()
|
| D | keep-tracking.c | 58 * test__keep_tracking - test using a dummy software event to keep tracking.
60 * This function implements a test that checks that tracking events continue
125 pr_debug("First time, failed to find tracking event.\n"); in test__keep_tracking()
147 pr_debug("Second time, failed to find tracking event.\n"); in test__keep_tracking()
|
| /Linux-v5.15/include/net/netfilter/ |
| D | nf_conntrack_core.h | 4 * standalone connection tracking module, and the compatibility layer's use
5 * of connection tracking.
22 standalone connection tracking module, and the compatibility layer's use
23 of connection tracking. */
|
| /Linux-v5.15/include/linux/ |
| D | context_tracking.h | 89 * ct_state() - return the current context tracking state if known
91 * Returns the current cpu's context tracking state if context tracking
92 * is enabled. If context tracking is disabled, returns
|
| D | entry-common.h | 109 * 2) Invoke context tracking if enabled to reactivate RCU
132 * This handles lockdep, RCU (context tracking) and tracing state, i.e.
262 * invoked after context tracking switched to user mode.
308 * 2) Invoke context tracking if enabled to adjust RCU state
358 * 3) Final transition (lockdep, tracing, context tracking, RCU), i.e. the
376 * The function establishes state (lockdep, RCU (context tracking), tracing)
420 * irqentry_enter - Handle state tracking on ordinary interrupt entries
424 * - lockdep irqflag state tracking as low level ASM entry disabled
427 * - Context tracking if the exception hit user mode.
|
| D | psi_types.h | 21 * don't have to special case any state tracking for it.
90 /* PSI growth tracking window */
124 /* Tracking window */
141 /* Per-cpu task state & time tracking */
|
| /Linux-v5.15/Documentation/vm/damon/ |
| D | faq.rst | 18 Can 'idle pages tracking' or 'perf mem' substitute DAMON?
21 Idle page tracking is a low level primitive for access check of the physical
26 Therefore, 'idle pages tracking' and 'perf mem' could provide a subset of
39 Nonetheless, DAMON provides vma tracking and PTE Accessed bit check based
|
| D | design.rst | 46 mapped to the physical memory and accessed. Thus, tracking the unmapped
48 level of noise using the adaptive regions adjustment mechanism, tracking every
79 other kernel subsystems using the Accessed bits, namely Idle page tracking and
81 exclusive with Idle page tracking and uses ``PG_idle`` and ``PG_young`` page
82 flags to solve the conflict with the reclaim logic, as Idle page tracking does.
|
| /Linux-v5.15/kernel/ |
| D | context_tracking.c | 3 * Context tracking: Probe on high level context boundaries such as kernel
42 WARN_ONCE((recursion < 1), "Invalid context tracking recursion value %d\n", recursion); in context_tracking_recursion_enter()
54 * context_tracking_enter - Inform the context tracking that the CPU is going
88 * Even if context tracking is disabled on this CPU, because it's outside in __context_tracking_enter()
135 * context_tracking_exit - Inform the context tracking that the CPU is
|
| /Linux-v5.15/Documentation/admin-guide/mm/ |
| D | idle_page_tracking.rst | 4 Idle Page Tracking
10 The idle page tracking feature allows to track which memory pages are being
23 The idle page tracking API is located at ``/sys/kernel/mm/page_idle``.
101 The idle memory tracking feature adds a new page flag, the Idle flag. This flag
116 Since the idle memory tracking feature is based on the memory reclaimer logic,
|
| D | soft-dirty.rst | 8 writes to. In order to do this tracking one should
24 Internally, to do this tracking, the writable bit is cleared from PTEs
35 While in most cases tracking memory changes by #PF-s is more than enough
|
| /Linux-v5.15/drivers/gpu/drm/i915/display/ |
| D | intel_frontbuffer.c | 28 * DOC: frontbuffer tracking
70 * @frontbuffer_bits: frontbuffer plane tracking bits
102 * @frontbuffer_bits: frontbuffer plane tracking bits
124 * @frontbuffer_bits: frontbuffer plane tracking bits
147 * @frontbuffer_bits: frontbuffer plane tracking bits
293 * intel_frontbuffer_track - update frontbuffer tracking
298 * This updates the frontbuffer tracking bits @frontbuffer_bits by clearing them
|
| /Linux-v5.15/Documentation/input/ |
| D | multi-touch-protocol.rst | 22 devices capable of tracking identifiable contacts (type B), the protocol
62 important. Event filtering and finger tracking is left to user space [#f3]_.
67 the ABS_MT_TRACKING_ID of the associated slot. A non-negative tracking id
69 tracking id not previously present is considered new, and a tracking id no
80 tracking more contacts than it is currently reporting, the driver should use
382 Finger Tracking
385 The process of finger tracking, i.e., to assign a unique trackingID to each
415 .. [#f5] See the section on finger tracking.
|
| /Linux-v5.15/arch/x86/kvm/mmu/ |
| D | page_track.c | 3 * Support KVM gust page tracking
76 * add guest page to the tracking pool so that corresponding access on that
85 * @mode: tracking mode, currently only write track is supported.
110 * remove the guest page from the tracking pool which stops the interception
120 * @mode: tracking mode, currently only write track is supported.
|
| /Linux-v5.15/drivers/iio/imu/inv_icm42600/ |
| D | Kconfig | 13 This driver supports the InvenSense ICM-426xx motion tracking
25 This driver supports the InvenSense ICM-426xx motion tracking
|
| /Linux-v5.15/include/linux/input/ |
| D | mt.h | 18 #define INPUT_MT_TRACK 0x0008 /* use in-kernel tracking */
35 * @trkid: stores MT tracking ID for the next contact
40 * @red: reduced cost matrix for in-kernel tracking
|
| /Linux-v5.15/drivers/iio/imu/inv_mpu6050/ |
| D | Kconfig | 20 and IAM20680 motion tracking devices over I2C.
32 and IAM20680 motion tracking devices over SPI.
|
