| /openbmc/linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_ref_tracking.c | 111 __description("reference tracking: leak potential reference")
126 __description("reference tracking: leak potential reference to sock_common")
141 __description("reference tracking: leak potential reference on stack")
159 __description("reference tracking: leak potential reference on stack 2")
179 __description("reference tracking: zero potential reference")
194 __description("reference tracking: zero potential reference to sock_common")
209 __description("reference tracking: copy and zero potential references")
226 __description("reference tracking: acquire/release user key reference")
246 __description("reference tracking: acquire/release system key reference")
265 __description("reference tracking: release user key reference without check")
[all …]
|
| /openbmc/linux/net/netfilter/ |
| H A D | Kconfig | 83 tristate "Netfilter connection tracking support"
88 Connection tracking keeps a record of what packets have passed
115 bool 'Connection mark tracking support'
124 bool 'Connection tracking security mark support'
137 bool 'Connection tracking zones'
140 This option enables support for connection tracking zones.
142 identity. Connection tracking zones allow to have multiple
158 bool "Connection tracking events"
161 If this option is enabled, the connection tracking code will
163 to get notified about changes in the connection tracking state.
[all …]
|
| /openbmc/qemu/docs/devel/migration/ |
| H A D | vfio.rst | 92 System memory dirty pages tracking
96 the VFIO dirty tracking module to start and stop dirty page tracking. A
98 dirty tracking module and marks system memory pages which were DMA-ed by the
101 Currently there are two ways dirty page tracking can be done:
102 (1) Device dirty tracking:
104 method can be used only if the device is capable of tracking its DMAs.
105 Discovering device capability, starting and stopping dirty tracking, and
113 In this method dirty tracking is done by IOMMU. However, there is currently no
114 IOMMU support for dirty page tracking. For this reason, all pages are
128 QEMU also provides a per device opt-out option ``pre-copy-dirty-page-tracking``
[all …]
|
| /openbmc/linux/kernel/time/ |
| H A D | Kconfig | 156 tracking to enter/exit RCU extended quiescent states.
159 bool "Force user context tracking"
164 support the user context tracking subsystem. But there are also
169 user context tracking backend but doesn't yet fulfill all the
172 for user context tracking and the subsystems that rely on it: RCU
175 dynticks subsystem by forcing the user context tracking on all
179 architecture backend for the user context tracking.
|
| /openbmc/linux/Documentation/networking/ |
| H A D | nf_conntrack-sysctl.rst | 14 Enable connection tracking flow accounting. 64-bit byte and packet
30 considered for connection tracking.
40 If this option is enabled, the connection tracking code will
41 provide userspace with connection tracking events via ctnetlink.
96 Maximum number of allowed connection tracking entries. This value is set
98 Note that connection tracking entries are added to the table twice -- once
164 Enable connection tracking flow timestamping.
|
| H A 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
|
| /openbmc/linux/drivers/staging/rtl8723bs/hal/ |
| H A 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()
|
| /openbmc/linux/drivers/gpu/drm/vmwgfx/ |
| H A D | vmwgfx_page_dirty.c | 31 * Different methods for tracking dirty:
80 * dirty-tracking method.
112 * vmw_bo_dirty_scan_mkwrite - Reset the mkwrite dirty-tracking method
118 * This function may change the dirty-tracking method.
158 * tracking structure
161 * This function may change the dirty tracking method.
221 * vmw_bo_dirty_add - Add a dirty-tracking user to a buffer object
224 * This function registers a dirty-tracking user to a buffer object.
278 * vmw_bo_dirty_release - Release a dirty-tracking user from a buffer object
281 * This function releases a dirty-tracking user from a buffer object.
[all …]
|
| /openbmc/linux/drivers/soc/aspeed/ |
| H A 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 …]
|
| /openbmc/linux/drivers/net/ethernet/intel/ice/ |
| H A D | ice_vf_mbx.c | 98 * ice_mbx_reset_vf_info() for each VF tracking structure.
105 * 4. Every time a message is read from the MBX queue, a tracking structure
114 * structure for each VF. The PF should clear the VF tracking structure if the
188 * @vf_info: mailbox tracking structure for a VF
249 * @vf_info: mailbox tracking structure for the VF in question in ice_mbx_vf_state_handler()
370 * @vf_info: the mailbox tracking structure for a VF
373 * current mailbox tracking state.
382 * ice_mbx_init_vf_info - Initialize a new VF mailbox tracking info
384 * @vf_info: the mailbox tracking info structure for a VF
386 * Initialize a VF mailbox tracking inf
[all...] |
| /openbmc/qemu/hw/vfio/ |
| H A D | common.c | 855 * The latter would otherwise generate large ranges for tracking, stressing in vfio_dirty_tracking_update_range()
898 .name = "vfio-tracking",
921 * to dirty tracking. Unregister it after we are done as we are not in vfio_dirty_tracking_init()
953 VFIODirtyRanges *tracking) in vfio_device_feature_dma_logging_start_create() argument
978 control->num_ranges = !!tracking->max32 + !!tracking->max64 + in vfio_device_feature_dma_logging_start_create()
979 !!tracking->maxpci64; in vfio_device_feature_dma_logging_start_create()
990 if (tracking->max32) { in vfio_device_feature_dma_logging_start_create()
991 ranges->iova = tracking->min32; in vfio_device_feature_dma_logging_start_create()
992 ranges->length = (tracking->max32 - tracking->min32) + 1; in vfio_device_feature_dma_logging_start_create()
995 if (tracking->max64) { in vfio_device_feature_dma_logging_start_create()
[all …]
|
| /openbmc/linux/tools/perf/tests/ |
| H A D | switch-tracking.c | 319 * test__switch_tracking - test using sched_switch and tracking events.
322 * tracking events can be recorded for a workload (current process) using the
323 * evsel->core.system_wide and evsel->tracking flags (respectively) with other events
441 /* Check tracking event is tracking */ in test__switch_tracking()
443 pr_debug("Tracking event not tracking\n"); in test__switch_tracking()
447 /* Check non-tracking events are not tracking */ in test__switch_tracking()
451 pr_debug("Non-tracking event is tracking\n"); in test__switch_tracking()
547 /* Check all 4 comm events were seen i.e. that evsel->tracking works */ in test__switch_tracking()
|
| H A 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()
164 DEFINE_SUITE("Use a dummy software event to keep tracking", keep_tracking);
|
| /openbmc/openbmc/poky/meta/recipes-graphics/wayland/ |
| H A D | mtdev_1.1.7.bb | 5 be from any MT device, specifically type A without contact tracking, type A with \
6 contact tracking, or type B with contact tracking"
|
| /openbmc/linux/kernel/ |
| H A D | context_tracking.c | 3 * Context tracking: Probe on high level context boundaries such as kernel,
9 * User/guest tracking started by Frederic Weisbecker:
446 WARN_ONCE((recursion < 1), "Invalid context tracking recursion value %d\n", recursion); in context_tracking_recursion_enter()
458 * __ct_user_enter - Inform the context tracking that the CPU is going
516 * Even if context tracking is disabled on this CPU, because it's outside in __ct_user_enter()
529 /* Tracking for vtime only, no concurrent RCU EQS accounting */ in __ct_user_enter()
533 * Tracking for vtime and RCU EQS. Make sure we don't race in __ct_user_enter()
553 * responsibility to call into context tracking with IRQs disabled.
579 * archs that didn't manage to check the context tracking
586 * responsibility to call into context tracking with IRQs disabled.
[all …]
|
| /openbmc/linux/include/net/netfilter/ |
| H A 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. */
|
| /openbmc/linux/include/linux/ |
| H A D | context_tracking_state.h | 122 * ct_state() - return the current context tracking state if known
124 * Returns the current cpu's context tracking state if context tracking
125 * is enabled. If context tracking is disabled, returns
|
| H A D | entry-common.h | 89 * 2) Invoke context tracking if enabled to reactivate RCU
112 * This handles lockdep, RCU (context tracking) and tracing state, i.e.
242 * invoked after context tracking switched to user mode.
268 * 2) Invoke context tracking if enabled to adjust RCU state
318 * 3) Final transition (lockdep, tracing, context tracking, RCU), i.e. the
336 * The function establishes state (lockdep, RCU (context tracking), tracing)
380 * irqentry_enter - Handle state tracking on ordinary interrupt entries
384 * - lockdep irqflag state tracking as low level ASM entry disabled
387 * - Context tracking if the exception hit user mode.
|
| /openbmc/linux/Documentation/admin-guide/mm/ |
| H A D | idle_page_tracking.rst | 2 Idle Page Tracking
8 The idle page tracking feature allows to track which memory pages are being
21 The idle page tracking API is located at ``/sys/kernel/mm/page_idle``.
98 The idle memory tracking feature adds a new page flag, the Idle flag. This flag
113 Since the idle memory tracking feature is based on the memory reclaimer logic,
|
| H A D | soft-dirty.rst | 6 writes to. In order to do this tracking one should
22 Internally, to do this tracking, the writable bit is cleared from PTEs
33 While in most cases tracking memory changes by #PF-s is more than enough
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A 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
281 * intel_frontbuffer_track - update frontbuffer tracking
286 * This updates the frontbuffer tracking bits @frontbuffer_bits by clearing them
|
| /openbmc/linux/Documentation/input/ |
| H A 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.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-filter/libnetfilter/ |
| H A D | libnetfilter-cttimeout_1.0.1.bb | 1 SUMMARY = "Netfilter connection tracking timeout library"
2 …ing interface (API) to the Linux kernel netfilter fine-grain connection tracking timeout infrastru…
|
| H A D | libnetfilter-conntrack_1.1.0.bb | 1 SUMMARY = "Netfilter connection tracking library"
2 …viding a programming interface (API) to the Linux kernel netfilter connection tracking state table"
|
| /openbmc/linux/net/ |
| H A D | Kconfig.debug | 4 bool "Enable net device refcount tracking"
13 bool "Enable networking namespace refcount tracking"
|