Home
last modified time | relevance | path

Searched full:since (Results 1 – 25 of 6510) sorted by relevance

12345678910>>...261

/linux-6.12.1/tools/bpf/bpftool/Documentation/
Dbpftool-cgroup.rst95 - **ingress** ingress path of the inet socket (since 4.10)
96 - **egress** egress path of the inet socket (since 4.10)
97 - **sock_create** opening of an inet socket (since 4.10)
98 - **sock_ops** various socket operations (since 4.12)
99 - **device** device access (since 4.15)
100 - **bind4** call to bind(2) for an inet4 socket (since 4.17)
101 - **bind6** call to bind(2) for an inet6 socket (since 4.17)
102 - **post_bind4** return from bind(2) for an inet4 socket (since 4.17)
103 - **post_bind6** return from bind(2) for an inet6 socket (since 4.17)
104 - **connect4** call to connect(2) for an inet4 socket (since 4.17)
[all …]
/linux-6.12.1/lib/
Derrseq.c10 * number of "subscribers" to tell whether it has changed since a previous
19 * can later be used to tell whether any new errors have occurred since that
23 * frequently, since we have so few bits to use as a counter.
26 * been sampled since a new value was recorded. That allows us to avoid bumping
27 * the counter if no one has sampled it since the last time an error was
33 * has ever been an error set since it was first initialized.
135 * errseq_check() - Has an error occurred since a particular sample point?
137 * @since: Previously-sampled errseq_t from which to check.
139 * Grab the value that eseq points to, and see if it has changed @since
140 * the given value was sampled. The @since value is not advanced, so there
[all …]
/linux-6.12.1/Documentation/core-api/
Derrseq.rst6 number of "subscribers" to tell whether it has changed since a previous
19 frequently, since we have so few bits to use as a counter.
22 a flag to tell whether the value has been sampled since a new value was
24 sampled it since the last time an error was recorded.
36 any new errors have occurred since that sampling was done, and atomically
39 can tell whether the value has changed since they last checked it.
44 has ever been an error set since it was first initialized.
57 far and whether he made any mistakes since they last asked.
111 whether one was made since they last checked, and the latest value
122 errseq_t since = errseq_sample(&wd.wd_err);
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/
Dinstruction.json105 …"PublicDescription": "Prefetch response received but was dropped since we don't support inflight u…
108 …"BriefDescription": "Prefetch response received but was dropped since we don't support inflight up…
117 "PublicDescription": "Prefetch request dropped since duplicate was found in TLB.",
120 "BriefDescription": "Prefetch request dropped since duplicate was found in TLB."
123 "PublicDescription": "Prefetch request dropped since it was found in cache.",
126 "BriefDescription": "Prefetch request dropped since it was found in cache."
/linux-6.12.1/tools/testing/selftests/powerpc/pmu/event_code_tests/
Devent_alternatives_tests_p9.c33 * PVR check is used here since PMU specific data like in event_alternatives_tests_p9()
50 * Expected to pass since PM_RUN_CYC_ALT in PMC2 has alternative event in event_alternatives_tests_p9()
63 * Expected to pass since PM_INST_DISP in PMC2 has alternative event in event_alternatives_tests_p9()
76 * Expected to pass since PM_BR_2PATH in PMC2 has alternative event in event_alternatives_tests_p9()
89 * Expected to pass since PM_LD_MISS_L1 in PMC3 has alternative event in event_alternatives_tests_p9()
102 * Expected to pass since PM_RUN_INST_CMPL_ALT in PMC4 has alternative event in event_alternatives_tests_p9()
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen3/
Dfloating-point.json6 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
13 …represents a one-cycle dispatch event. This event is a speculative event. Since this event include…
20 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
27 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
34 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
46 …ycle can vary from 0 to 64. This event requires the use of the MergeEvent since it can count above…
52 …ycle can vary from 0 to 64. This event requires the use of the MergeEvent since it can count above…
58 …ycle can vary from 0 to 64. This event requires the use of the MergeEvent since it can count above…
64 …ycle can vary from 0 to 64. This event requires the use of the MergeEvent since it can count above…
/linux-6.12.1/tools/include/linux/
Dring_buffer.h12 * Since the mmap() consumer (userspace) can run on a
31 * D needs to be a full barrier since it separates the data
34 * For B a WMB is sufficient since it separates two WRITEs,
35 * and for C an RMB is sufficient since it separates two READs.
41 * supported architectures since for a fair number it would
/linux-6.12.1/include/uapi/linux/
Dppp_defs.h143 * The following structure records the time in seconds since
151 __kernel_old_time_t xmit_idle; /* time since last NP packet sent */
152 __kernel_old_time_t recv_idle; /* time since last NP packet received */
156 __s32 xmit_idle; /* time since last NP packet sent */
157 __s32 recv_idle; /* time since last NP packet received */
161 __s64 xmit_idle; /* time since last NP packet sent */
162 __s64 recv_idle; /* time since last NP packet received */
Dvbox_vmmdev_types.h33 VMMDEVREQ_REGISTER_PATCH_MEMORY = 22, /* since version 3.0.6 */
34 VMMDEVREQ_DEREGISTER_PATCH_MEMORY = 23, /* since version 3.0.6 */
39 VMMDEVREQ_REPORT_GUEST_INFO2 = 58, /* since version 3.2.0 */
40 VMMDEVREQ_REPORT_GUEST_STATUS = 59, /* since version 3.2.8 */
41 VMMDEVREQ_REPORT_GUEST_USER_STATE = 74, /* since version 4.3 */
64 VMMDEVREQ_VIDEMODE_SUPPORTED2 = 57, /* since version 3.2.0 */
65 VMMDEVREQ_GET_DISPLAY_CHANGE_REQEX = 80, /* since version 4.2.4 */
92 VMMDEVREQ_GET_SESSION_ID = 217, /* since version 3.2.8 */
/linux-6.12.1/drivers/media/test-drivers/vivid/
Dvivid-kthread-touch.c90 /* Calculate the number of jiffies since we started streaming */ in vivid_thread_touch_cap()
92 /* Get the number of buffers streamed since the start */ in vivid_thread_touch_cap()
100 * jiffies have passed since we started streaming reset the in vivid_thread_touch_cap()
117 * since we started, including the current buffer. in vivid_thread_touch_cap()
121 /* And the number of jiffies since we started */ in vivid_thread_touch_cap()
128 * in jiffies since we started streaming. in vivid_thread_touch_cap()
/linux-6.12.1/tools/testing/selftests/arm64/signal/
Dtest_signals_utils.h34 * dedicated signal handler, since there, it is populated by Kernel
39 * because here we have to avoid syscalls to trigger the signal since
50 * in such a case return 0, since in fact we have not just simply grabbed
90 * struct tdescr since it will be changed inside the in get_current_context()
98 * test thread. Since such delivery happens on the ret_to_user() in get_current_context()
106 * - note that since we are using a breakpoint instruction here in get_current_context()
/linux-6.12.1/Documentation/sound/cards/
Dhdspm.rst10 Full functionality has been added to the driver. Since some of
25 since unused DMA channels are disabled and less memory is
74 where DMA reads/writes. Since of the bulk mode of PCI it is only
98 Since DSP-MADI-Mixer has 8152 Fader, it does not make sense to
99 use the standard mixer-controls, since this would break most of
105 hwdep-interface. Since it could be a performance problem always
133 frequency or slave), since even not using an Audio-application
168 Note: Since MADI has a much higher bit-rate than word-clock, the
169 card should synchronise better in MADI Mode. But since the
/linux-6.12.1/Documentation/admin-guide/LSM/
DSafeSetID.rst18 capabilities, since using file capabilities to run a program with elevated
19 privileges opens up possible security holes since any user with access to the
25 since CAP_SETUID allows changing to any user on the system, including the root
27 especially since programs often only call setuid() to drop privileges to a
38 of CAP_SETUID since the non-root program cannot take advantage of CAP_SETUID to
92 "Since setuid only affects the current process, and since the SELinux controls
/linux-6.12.1/rust/kernel/
Dkunit.rs13 /// Public but hidden since it should only be used from KUnit generated code.
29 /// Public but hidden since it should only be used from KUnit generated code.
45 /// Public but hidden since it should only be used from generated tests.
81 " Failure not reported to KUnit since this is a non-KUnit task\n"
116 // strings since they are `CStr`s.
118 // - The pointers passed will remain valid since they point to `static`s.
151 /// Public but hidden since it should only be used from generated tests.
/linux-6.12.1/sound/soc/fsl/
DKconfig14 This option is only useful for out-of-tree drivers since
26 This option is only useful for out-of-tree drivers since
36 This option is only useful for out-of-tree drivers since
54 This option is only useful for out-of-tree drivers since
67 This option is only useful for out-of-tree drivers since
77 This option is only useful for out-of-tree drivers since
131 This option is only useful for out-of-tree drivers since
159 This option is only useful for out-of-tree drivers since
/linux-6.12.1/Documentation/devicetree/bindings/iio/temperature/
Dmelexis,mlx90632.yaml19 object temperature range for industrial applications. Since it can
27 Since measured object emissivity effects Infra Red energy emitted,
36 degree Celsius for human body measurement applications. Since it can
40 Since measured object emissivity effects Infra Red energy emitted,
/linux-6.12.1/tools/perf/pmu-events/arch/x86/amdzen1/
Dfloating-point.json6 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
13 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
20 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
27 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
34 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
41 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
48 …represents a one-cycle dispatch event. This event is a speculative event. Since this event include…
55 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
62 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
69 …epresents a one- cycle dispatch event. This event is a speculative event. Since this event include…
/linux-6.12.1/Documentation/ABI/obsolete/
Dsysfs-bus-iio7 Since Kernel 5.11, multiple buffers are supported.
19 Since Kernel 5.11, multiple buffers are supported.
31 Since kernel 5.11 the scan_elements attributes are merged into
66 Since kernel 5.11 the scan_elements attributes are merged into
108 Since kernel 5.11 the scan_elements attributes are merged into
147 Since kernel 5.11 the scan_elements attributes are merged into
168 Since Kernel 5.11, multiple buffers are supported.
183 Since Kernel 5.11, multiple buffers are supported.
/linux-6.12.1/Documentation/admin-guide/
Dunicode.rst31 In particular, ESC ( U is no longer "straight to font", since the font
42 refers to this as a "Corporate Zone", since this is inaccurate for
44 point since it lets the direct-mapping area start on a large power of
72 omitted the scan 5 line, since it is also used as a block-graphics
81 since they are horribly vendor-specific. This, of course, is an
106 Since the characters in the beginning of the Linux CZ have been more
122 However, since the set of symbols appear to be consistent throughout,
175 Since the assignment of the Klingon Linux Unicode block, a registry of
Diostats.rst5 Since 2.4.20 (and some versions before, with patches), and 2.5.45,
53 All fields except field 9 are cumulative since boot. Field 9 should
101 Since 5.0 this field counts jiffies when at least one request was
108 (field 9) times the number of milliseconds spent doing I/O since the
146 Since 4.19 request times are measured with nanoseconds precision and
175 Note that since the address is translated to a disk-relative one, and no
183 reads/writes before merges for partitions and after for disks. Since a
189 disk and partition statistics are consistent again. Since we still don't
/linux-6.12.1/Documentation/admin-guide/mm/
Dpagemap.rst21 * Bit 56 page exclusively mapped (since 4.2)
22 * Bit 57 pte is uffd-wp write-protected (since 5.13) (see
25 * Bit 61 page is file-page or shared-anon (since 3.5)
29 Since Linux 4.0 only users with the CAP_SYS_ADMIN capability can get PFNs.
127 The page has not been accessed since it was marked idle (see
161 The page has been referenced since last LRU list enqueue/requeue.
206 always 12 at most architectures). Since Linux 3.11 their meaning changes
207 after first clear of soft-dirty bits. Since Linux 4.2 they are used for
297 have been written to since they were last marked and/or optionally write protect
/linux-6.12.1/Documentation/scsi/
DChangeLog.sym53c8xx70 This parameter wasn't that clever since we can use "sync:"
216 Code moved from the FreeBSD sym_hipd driver, since it has
219 function chips, since I cannot make sure for what chip revisions
230 io_request_lock since it seems to be a definite feature now.:)
231 - Change get_pages by GetPages since Linux >= 2.3.27 now wants
254 - Remove the quirk handling that has been useless since day one.
344 result is greater than 37 MHz. Since the precision of the
388 - Do a normal soft reset as first chip reset, since aborting current
389 operation may raise an interrupt we are not able to handle since
404 the scatterlist instead of the data.:) Since this should never
[all …]
/linux-6.12.1/include/linux/
Dcompiler_attributes.h37 * Note: do not use this directly. Instead, use __alloc_size() since it is conditionally
86 * Optional: only supported since gcc >= 9
98 * Optional: only supported since gcc >= 15
99 * Optional: only supported since clang >= 18
112 * Optional: only supported since clang >= 14.0
146 * Optional: only supported since clang >= 14.0
193 * Optional: only supported since gcc >= 7
247 * Optional: only supported since gcc >= 8
259 * Optional: only supported since GCC >= 7.1, clang >= 13.0.
278 * Optional: only supported since GCC >= 11.1, clang >= 7.0.
[all …]
/linux-6.12.1/tools/perf/pmu-events/arch/x86/silvermont/
Dvirtual-memory.json17 …e when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk implies…
36 …": "This event counts when a data (D) page walk is completed or started. Since a page walk implie…
55 … event counts when an instruction (I) page walk is completed or started. Since a page walk implie…
65 …a (D) page walk or an instruction (I) page walk is completed or started. Since a page walk implie…
/linux-6.12.1/Documentation/locking/
Drt-mutex-design.rst38 meantime, B executes, and since B is of a higher priority than C, it preempts C,
69 of A. So now if B becomes runnable, it would not preempt C, since C now has
102 process. Since the scope of the waiter is within the code for
133 would never diverge, since a process can't be blocked on more than one
161 Since a process may own more than one mutex, but never be blocked on more than
176 Also since a mutex may have more than one process blocked on it, we can
228 defined. But is very complex to figure it out, since it depends on all
293 Now since mutexes can be defined by user-land applications, we don't want a DOS
305 mutex is not owned, this owner is set to NULL. Since all architectures
332 This is really nice to have, since it allows you to only update a variable
[all …]

12345678910>>...261