/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 …]
|
/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
|
/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
|
/Documentation/devicetree/bindings/iio/temperature/ |
D | mlx90632.txt | 9 industrial applications. Since it can operate and measure ambient temperature 16 Since measured object emissivity effects Infra Red energy emitted, emissivity
|
/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 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
|
/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
|
D | soft-dirty.rst | 21 written to since step 1. 31 This is so, since the pages are still mapped to physical memory, and thus all
|
D | idle_page_tracking.rst | 32 A page is considered idle if it has not been accessed since it was marked idle 64 If one wants to ignore certain types of pages, e.g. mlocked pages since they 116 Since the idle memory tracking feature is based on the memory reclaimer logic, 119 since there are usually not many of them, it should not affect the overall
|
/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.
|
/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
|
/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
|
/Documentation/userspace-api/media/dvb/ |
D | video-get-frame-count.rst | 47 - Returns the number of frames displayed since the decoder was 58 frames since the decoder was started.
|
/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 …]
|
/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 …]
|
/Documentation/fb/ |
D | tgafb.rst | 17 Major new features since Linux 2.0.x: 23 User-visible changes since Linux 2.2.x: 58 The XFree86 FBDev server has been reported not to work, since tgafb doesn't do
|
/Documentation/ABI/testing/ |
D | configfs-stp-policy-p_sys-t | 29 passed since the previous packet from this source. Zero is 37 this many milliseconds have passed since the previous
|
D | sysfs-devices-edac | 7 long since the last counter were reset. This is useful for 8 computing errors/time. Since the counters are always reset 16 since the last counter reset. This can be used with the error 37 increment, since EDAC will panic the system 156 counter will not have a chance to increment, since EDAC will panic the
|
D | sysfs-kernel-oops_count | 6 Shows how many times the system has Oopsed since last boot.
|
/Documentation/admin-guide/cgroup-v1/ |
D | hugetlb.rst | 70 control group and enforces the limit during page fault. Since HugeTLB 88 HugeTLB memory for which no reservation exists. Since reservation limits are 95 Reservation limits are superior to page fault limits described above, since 100 hard to avoid processes getting SIGBUS since the sysadmin needs precisely know
|
/Documentation/userspace-api/media/v4l/ |
D | pixfmt-compressed.rst | 41 then the decoder has no requirements since it can parse all the 97 then the decoder has no requirements since it can parse all the 106 then the decoder has no requirements since it can parse all the 186 then the decoder has no requirements since it can parse all the 219 since the decoder can parse all the information from the raw bytestream.
|
/Documentation/devicetree/bindings/arm/ |
D | coresight-cpu-debug.txt | 15 "arm,primecell" since this driver is using the AMBA bus 22 - clock-names : the name of the clock referenced by the code. Since we are
|
/Documentation/virt/kvm/ |
D | locking.rst | 58 The mapping from gfn to pfn may be changed since we can only ensure the pfn 98 For direct sp, we can easily avoid it since the spte of direct sp is fixed 114 spte is read-only and the Accessed bit has already been set since the 117 But it is not true after fast page fault since the spte can be marked 171 be flushed caused by this reason in mmu_spte_update() since this is a common 174 Since the spte is "volatile" if it can be updated out of mmu-lock, we always 219 :Comment: it is a spinlock since it is used in mmu notifier. 240 wakeup notification event since external interrupts from the
|
/Documentation/powerpc/ |
D | dawr-power9.rst | 44 will accept the command. Unfortunately since there is no hardware 54 speed since it can use the hardware emulation. Unfortunately if this 62 Kernels (since ~v5.2) have an option to force enable the DAWR via::
|
/Documentation/driver-api/md/ |
D | raid5-cache.rst | 8 since 4.4) or write-back mode (supported since 4.10). mdadm (supported since 50 write-back mode fixes the 'write hole' issue too, since all write data is
|