since (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...238

/kernel/linux/linux-5.10/tools/bpf/bpftool/Documentation/
D	bpftool-cgroup.rst	84 ingress ingress path of the inet socket (since 4.10); 85 egress egress path of the inet socket (since 4.10); 86 sock_create opening of an inet socket (since 4.10); 87 sock_ops various socket operations (since 4.12); 88 device device access (since 4.15); 89 bind4 call to bind(2) for an inet4 socket (since 4.17); 90 bind6 call to bind(2) for an inet6 socket (since 4.17); 91 post_bind4 return from bind(2) for an inet4 socket (since 4.17); 92 post_bind6 return from bind(2) for an inet6 socket (since 4.17); 93 connect4 call to connect(2) for an inet4 socket (since 4.17); [all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-5.10/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,`
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/include/uapi/linux/
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 */`
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 */
/kernel/linux/linux-5.10/tools/testing/selftests/arm64/signal/
D	test_signals_utils.h	`30 * dedicated signal handler, since there, it is populated by Kernel 35 * because here we have to avoid syscalls to trigger the signal since 46 * in such a case return 0, since in fact we have not just simply grabbed 73 * struct tdescr since it will be changed inside the in get_current_context() 81 * test thread. Since such delivery happens on the ret_to_user() in get_current_context() 89 * - note that since we are using a breakpoint instruction here in get_current_context()`
/kernel/linux/linux-5.10/drivers/media/test-drivers/vivid/
D	vivid-kthread-touch.c	85 /* Calculate the number of jiffies since we started streaming / in vivid_thread_touch_cap() 87 / Get the number of buffers streamed since the start / in vivid_thread_touch_cap() 95 jiffies have passed since we started streaming reset the in vivid_thread_touch_cap() 110 * since we started, including the current buffer. in vivid_thread_touch_cap() 114 /* And the number of jiffies since we started / in vivid_thread_touch_cap() 121 in jiffies since we started streaming. in vivid_thread_touch_cap()
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/
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…
/kernel/linux/linux-5.10/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 35 This option is only useful for out-of-tree drivers since 53 This option is only useful for out-of-tree drivers since 65 This option is only useful for out-of-tree drivers since 75 This option is only useful for out-of-tree drivers since 110 This option is only useful for out-of-tree drivers since`
/kernel/linux/linux-5.10/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…`
/kernel/linux/linux-5.10/Documentation/admin-guide/
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 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
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
/kernel/linux/linux-5.10/include/linux/
D	time.h	`27 * 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 */`
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/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`
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-5.10/Documentation/process/
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
/kernel/linux/linux-5.10/Documentation/power/
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.
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/
D	i915_drv.h	1314 * Return true if revision is in range [since,until] inclusive. 1316 * Use 0 for open-ended since, and REVID_FOREVER for open-ended until. 1318 #define IS_REVID(p, since, until) \ argument 1319 (INTEL_REVID(p) >= (since) && INTEL_REVID(p) <= (until)) 1494 #define IS_SKL_REVID(p, since, until) (IS_SKYLAKE(p) && IS_REVID(p, since, until)) argument 1502 #define IS_BXT_REVID(dev_priv, since, until) \ argument 1503 (IS_BROXTON(dev_priv) && IS_REVID(dev_priv, since, until)) 1525 #define IS_KBL_GT_REVID(dev_priv, since, until) \ argument 1527 kbl_revids[INTEL_REVID(dev_priv)].gt_stepping >= since && \ 1529 #define IS_KBL_DISP_REVID(dev_priv, since, until) \ argument [all …]

12 3 4 5 6 7 8 9 10 >>...238