| /linux/tools/bpf/bpftool/Documentation/ |
| H A D | bpftool-cgroup.rst | 95 - **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/lib/ |
| H A D | errseq.c | 10 * 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/Documentation/core-api/ |
| H A D | errseq.rst | 6 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/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/ |
| H A D | instruction.json | 105 …"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/tools/testing/selftests/powerpc/pmu/event_code_tests/ |
| H A D | event_alternatives_tests_p9.c | 33 * 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/tools/perf/pmu-events/arch/x86/amdzen3/ |
| H A D | floating-point.json | 6 …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/tools/include/linux/ |
| H A D | ring_buffer.h | 12 * 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/include/uapi/linux/ |
| H A D | ppp_defs.h | 143 * 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 */
|
| H A D | vbox_vmmdev_types.h | 33 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/tools/testing/selftests/rtc/ |
| H A D | rtctest.c | 52 SKIP(return, "Skipping test since %s does not exist", rtc_file); in TEST_F()
121 SKIP(return, "Skipping test since %s does not exist", rtc_file);
159 SKIP(return, "Skipping test since %s does not exist", rtc_file);
188 SKIP(return, "Skipping test since %s does not exist", rtc_file); in TEST_F()
232 SKIP(return, "Skipping test since %s does not exist", rtc_file); in TEST_F()
237 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
239 SKIP(return, "Skipping test since alarms has only minute granularity."); in TEST_F()
302 SKIP(return, "Skipping test since %s does not exist", rtc_file); in TEST_F()
307 SKIP(return, "Skipping test since alarms are not supported."); in TEST_F()
309 SKIP(return, "Skipping test since alarms has only minute granularity."); in TEST_F()
[all …]
|
| /linux/Documentation/sound/cards/ |
| H A D | hdspm.rst | 10 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/Documentation/admin-guide/LSM/ |
| H A D | SafeSetID.rst | 18 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/rust/kernel/ |
| H A D | kunit.rs | 13 /// 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.
47 /// Public but hidden since it should only be used from generated tests.
83 " Failure not reported to KUnit since this is a non-KUnit task\n"
118 // strings since they are `CStr`s.
120 // - The pointers passed will remain valid since they point to `static`s.
153 /// Public but hidden since it should only be used from generated tests.
|
| /linux/sound/soc/fsl/ |
| H A D | Kconfig | 17 This option is only useful for out-of-tree drivers since
29 This option is only useful for out-of-tree drivers since
40 This option is only useful for out-of-tree drivers since
58 This option is only useful for out-of-tree drivers since
71 This option is only useful for out-of-tree drivers since
81 This option is only useful for out-of-tree drivers since
135 This option is only useful for out-of-tree drivers since
163 This option is only useful for out-of-tree drivers since
|
| /linux/Documentation/devicetree/bindings/iio/temperature/ |
| H A D | melexis,mlx90632.yaml | 19 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/tools/perf/pmu-events/arch/x86/amdzen1/ |
| H A D | floating-point.json | 6 …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/Documentation/ABI/obsolete/ |
| H A D | sysfs-bus-iio | 7 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/Documentation/admin-guide/ |
| H A D | unicode.rst | 31 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
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 70 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/tools/perf/pmu-events/arch/x86/silvermont/ |
| H A D | virtual-memory.json | 17 …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/Documentation/locking/ |
| H A D | rt-mutex-design.rst | 38 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 …]
|
| /linux/Documentation/RCU/ |
| H A D | UP.rst | 8 is that since there is only one CPU, it should not be necessary to
9 wait for anything else to get done, since there are no other CPUs for
45 RCU usage, since call_rcu() must wait for a grace period to elapse.
91 grace period has elapsed since those callbacks were queued. This is
134 then, since RCU callbacks can be invoked from softirq context,
139 This restriction might seem gratuitous, since very few RCU
|
| /linux/Documentation/power/ |
| H A D | suspend-and-cpuhotplug.rst | 157 argument. But during suspend, since the tasks are already frozen by the time
197 In this case since we probably need to apply different microcode revisions
212 Hence, when a new CPU is brought online, since the kernel finds that it
232 when the CPUs are brought back online, since they wouldn't have lost the
236 However, in the case of hibernation, since all the CPUs are completely
247 And during the CPU online operations (during resume/restore), since the
266 This might not reflect the true current state of the system, since the
277 into the kernel, since the freezing has not yet begun.
|
| /linux/Documentation/process/ |
| H A D | botching-up-ioctls.rst | 13 Which is nice, since there's no more insanity in the form of fake-generic, but
46 conversion or worse, fiddle the raw __u64 through your code since that
57 pain. And since getting things wrong on the first attempt is guaranteed you
62 rejecting the new flags/modes or ioctls (since doing that was botched in the
68 but isn't a complete solution since newer userspace on older kernels won't
74 future extensions is going right down the gutters since someone will submit
155 frame counter. With a spec lawyer hat on this isn't a bug since timeouts can
220 Finally, the name of the game is to get it right on the first attempt, since if
|
| /linux/Documentation/filesystems/ |
| H A D | directory-locking.rst | 167 Since the locking order is consistent with the ranking, all
195 have changed since the moment directory locks had been acquired,
199 Since all operations are on the same filesystem, there can't be
218 It can't be the parents - indeed, since D1 is an ancestor of Dn,
225 a loop, since the parents are locked before the children, so the parent
233 among the children, in some order. But that is also impossible, since
236 That concludes the proof, since the set of operations with the
255 Suppose after the operation there is a loop; since there hadn't been such
260 Since the operation has succeeded, neither source nor target could have
|