| /Linux-v5.4/lib/ |
| D | errseq.c | 9 * number of "subscribers" to tell whether it has changed since a previous
18 * can later be used to tell whether any new errors have occurred since that
22 * frequently, since we have so few bits to use as a counter.
25 * been sampled since a new value was recorded. That allows us to avoid bumping
26 * the counter if no one has sampled it since the last time an error was
32 * has ever been an error set since it was first initialized.
134 * errseq_check() - Has an error occurred since a particular sample point?
136 * @since: Previously-sampled errseq_t from which to check.
138 * Grab the value that eseq points to, and see if it has changed @since
139 * the given value was sampled. The @since value is not advanced, so there
[all …]
|
| /Linux-v5.4/tools/bpf/bpftool/Documentation/ |
| D | bpftool-cgroup.rst | 83 **ingress** ingress path of the inet socket (since 4.10);
84 **egress** egress path of the inet socket (since 4.10);
85 **sock_create** opening of an inet socket (since 4.10);
86 **sock_ops** various socket operations (since 4.12);
87 **device** device access (since 4.15);
88 **bind4** call to bind(2) for an inet4 socket (since 4.17);
89 **bind6** call to bind(2) for an inet6 socket (since 4.17);
90 **post_bind4** return from bind(2) for an inet4 socket (since 4.17);
91 **post_bind6** return from bind(2) for an inet6 socket (since 4.17);
92 **connect4** call to connect(2) for an inet4 socket (since 4.17);
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| 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-v5.4/arch/h8300/include/asm/ |
| D | hash.h | 7 * and H8S have only 16x16->32. Since it's tolerably compact, this is
8 * basically an inlined version of the __mulsi3 code. Since the inputs
12 * (Since neither CPU has any multi-bit shift instructions, a
16 * since that is heavily dependent on rotates. Which, as mentioned, suck
32 * This has been designed to modify x in place, since that's the most
33 * common usage, but preserve k, since hash_64() makes two calls in
|
| /Linux-v5.4/fs/ntfs/ |
| D | time.h | 26 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
28 * intervals since the value of tv_sec.
31 * measured as the number of 100-nano-second intervals since 1st January 1601,
66 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
68 * intervals since the value of tv_sec.
71 * measured as the number of 100 nano-second intervals since 1st January 1601,
|
| /Linux-v5.4/tools/include/linux/ |
| 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-v5.4/drivers/block/paride/ |
| D | Transition-notes | 8 anything except B, since it is under if (!ps_tq_active) under
9 ps_spinlock. C is always preceded by B, since we can't reach it
12 the sum of numbers of A and C, since each call of ps_tq_int() is
16 since at any time number of B can not exceed the number of these
87 we were acquiring the lock, (1) would be already false, since
98 pi_spinlock, or after not tocuhing ->claimed_cont since acquiring pi_spinlock
122 ps_continuation, since the latter is changed only from the area.
123 We don't need to reset it to NULL, since we are guaranteed that there
|
| /Linux-v5.4/Documentation/admin-guide/LSM/ |
| 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-v5.4/Documentation/virt/kvm/ |
| D | locking.txt | 52 The mapping from gfn to pfn may be changed since we can only ensure the pfn
81 For direct sp, we can easily avoid it since the spte of direct sp is fixed
96 spte is read-only and the Accessed bit has already been set since the
99 But it is not true after fast page fault since the spte can be marked
144 be flushed caused by this reason in mmu_spte_update() since this is a common
147 Since the spte is "volatile" if it can be updated out of mmu-lock, we always
192 Comment: it is a spinlock since it is used in mmu notifier.
213 wakeup notification event since external interrupts from the
|
| /Linux-v5.4/Documentation/sound/cards/ |
| 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-v5.4/include/linux/ |
| D | time.h | 28 * timer. Since these timers wrap every tick, they're not really
61 /* the number of months since January, in the range 0 to 11 */
63 /* the number of years since 1900 */
65 /* the number of days since Sunday, in the range 0 to 6 */
67 /* the number of days since January 1, in the range 0 to 365 */
|
| /Linux-v5.4/include/uapi/linux/ |
| 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 */
91 VMMDEVREQ_GET_SESSION_ID = 217, /* since version 3.2.8 */
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | unicode.rst | 32 In particular, ESC ( U is no longer "straight to font", since the font
43 refers to this as a "Corporate Zone", since this is inaccurate for
45 point since it lets the direct-mapping area start on a large power of
73 omitted the scan 5 line, since it is also used as a block-graphics
82 since they are horribly vendor-specific. This, of course, is an
107 Since the characters in the beginning of the Linux CZ have been more
123 However, since the set of symbols appear to be consistent throughout,
176 Since the assignment of the Klingon Linux Unicode block, a registry of
|
| D | iostats.rst | 5 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
100 Since 5.0 this field counts jiffies when at least one request was
107 (field 9) times the number of milliseconds spent doing I/O since the
162 Note that since the address is translated to a disk-relative one, and no
170 reads/writes before merges for partitions and after for disks. Since a
176 disk and partition statistics are consistent again. Since we still don't
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/silvermont/ |
| D | virtual-memory.json | 13 …": "This event counts when a data (D) page walk is completed or started. Since a page walk implie…
32 … event counts when an instruction (I) page walk is completed or started. Since a page walk implie…
51 …a (D) page walk or an instruction (I) page walk is completed or started. Since a page walk implie…
61 …e when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk implies…
|
| /Linux-v5.4/Documentation/scsi/ |
| 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-v5.4/Documentation/admin-guide/mm/ |
| D | pagemap.rst | 23 * Bit 56 page exclusively mapped (since 4.2)
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 page has not been accessed since it was marked idle (see
161 page has been referenced since last LRU list enqueue/requeue
205 always 12 at most architectures). Since Linux 3.11 their meaning changes
206 after first clear of soft-dirty bits. Since Linux 4.2 they are used for
|
| /Linux-v5.4/Documentation/locking/ |
| 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-v5.4/Documentation/ioctl/ |
| 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-v5.4/Documentation/power/ |
| D | suspend-and-cpuhotplug.rst | 157 argument. But during suspend, since the tasks are already frozen by the time
196 In this case since we probably need to apply different microcode revisions
211 Hence, when a new CPU is brought online, since the kernel finds that it
231 when the CPUs are brought back online, since they wouldn't have lost the
235 However, in the case of hibernation, since all the CPUs are completely
246 And during the CPU online operations (during resume/restore), since the
265 This might not reflect the true current state of the system, since the
276 into the kernel, since the freezing has not yet begun.
|
| /Linux-v5.4/sound/soc/fsl/ |
| D | Kconfig | 14 This option is only useful for out-of-tree drivers since
25 This option is only useful for out-of-tree drivers since
43 This option is only useful for out-of-tree drivers since
55 This option is only useful for out-of-tree drivers since
65 This option is only useful for out-of-tree drivers since
89 This option is only useful for out-of-tree drivers since
|
| /Linux-v5.4/arch/openrisc/include/asm/ |
| D | cacheflush.h | 21 * and instruction caches. SMP needs a little extra work, since we need
53 * Pages with this bit set need not be flushed/invalidated, since
54 * they have not changed since last flush. New pages start with
66 * Other interfaces are not required since we do not have virtually
|
| /Linux-v5.4/Documentation/RCU/ |
| 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.
125 then, since RCU callbacks can be invoked from softirq context,
130 This restriction might seem gratuitous, since very few RCU
|
| /Linux-v5.4/include/linux/mtd/ |
| D | onfi.h | 62 __le16 ext_param_page_length; /* since ONFI 2.1 */
63 u8 num_of_param_pages; /* since ONFI 2.1 */
122 /* Extended ECC information Block Definition (since ONFI 2.1) */
141 /* Extended Parameter Page Definition (since ONFI 2.1) */
|
| /Linux-v5.4/arch/arm/include/asm/ |
| D | dma.h | 96 * especially since some DMA architectures don't update the
104 * especially since some DMA architectures don't update the
114 * especially since some DMA architectures don't update the
122 * especially since some DMA architectures don't update the
|
