| /Documentation/core-api/ |
| D | timekeeping.rst | 21 accurately. Starts at system boot time but stops during suspend.
27 Like ktime_get(), but does not stop when suspended. This can be
38 persist across a reboot, like inode times, but should be avoided
47 Like ktime_get_real(), but uses the International Atomic Time (TAI)
55 Like ktime_get(), but runs at the same rate as the hardware
71 Same as the plain ktime_get functions, but returning a u64 number
81 Same above, but returns the time in a 'struct timespec64', split
117 These are quicker than the non-coarse versions, but less accurate,
126 but can't easily use 'jiffies', e.g. for inode timestamps.
128 on most modern machines with a reliable cycle counter, but
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 45 at boot but shouldn't prevent it from being turned off later.
129 protection and value '1' indicates that protection should be enabled but
136 that detection should be enabled but limit setting can be omitted.
140 is assumed still to be functional but approaching limit where it gets
143 be enabled but limit setting can be omitted.
148 protection and value '1' indicates that protection should be enabled but
156 that detection should be enabled but limit setting can be omitted. Limit
161 is assumed still to be functional but approaching limit where it gets
164 be enabled but limit setting can be omitted. Limit is given as microvolt
170 protection and value '1' indicates that protection should be enabled but
[all …]
|
| /Documentation/bpf/ |
| D | ringbuf.rst | 22 These two problems are independent, but perf buffer fails to satisfy both.
26 counting, but given the first one requires an MPSC buffer, the same solution
33 type ``BPF_MAP_TYPE_RINGBUF``. Two other alternatives considered, but
37 ``BPF_MAP_TYPE_RINGBUF`` could represent an array of ring buffers, but not
39 with existing perf buffer use in BPF, but would fail if application needed more
51 themselves with, new syntax in libbpf, etc. But then would really provide no
53 doesn't support lookup/update/delete operations, but so doesn't few other map
66 with hashed task's tgid being a look up key to preserve order, but reduce
81 - but still the ability to do busy polling for new data to achieve the
93 discarded. Discard is similar to commit, but makes consumer ignore the
[all …]
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 13 Which is nice, since there's no more insanity in the form of fake-generic, but
14 actually only used once interfaces. But the clear downside is that there's much
34 platforms don't necessarily align 64-bit values to 64-bit boundaries, but
68 but isn't a complete solution since newer userspace on older kernels won't
77 but garbage. This is also the reason why you must explicitly pad all
136 v4l use by default nowadays. But let userspace know which timestamps are
139 will mismatch if you look close enough, but if performance measuring tools
145 convenient time specification, but it's mostly the standard.
156 always be extended - but users will surely hate you if their neat animations
171 A full-blown drm driver essentially implements a little OS, but specialized to
[all …]
|
| D | volatile-considered-harmful.rst | 40 compiler might think it knows what will be in shared_data, but the
46 necessary. But the compiler would also be prevented from optimizing access
54 by locks, but one also does not want the compiler "optimizing" register
55 accesses within a critical section. But, within the kernel, I/O memory
81 - Inline assembly code which changes memory, but which has no other
86 every time it is referenced, but it can be read without any special
87 locking. So jiffies can be volatile, but the addition of other
|
| /Documentation/arch/arm64/ |
| D | cpu-hotplug.rst | 18 Physical systems need to mark a CPU that is ``possible`` but not ``present`` as
24 In the arm64 world CPUs are not a single device but a slice of the system.
29 e.g. New CPUs come with new caches, but the platform's cache topology is
35 structures can describe a redistributor associated with a disabled CPU, but
50 CPU Hotplug as all resources are described as ``present``, but CPUs may be
64 ``enabled`` in the MADT GICC structures, but should have the ``online capable``
69 CPUs described as ``online capable`` but not ``enabled`` can be set to enabled
|
| /Documentation/scheduler/ |
| D | sched-stats.rst | 23 domain. Domains have no particular names in this implementation, but
53 scheduler. We kept it for ABI compatibility, but it is always set to zero.
85 2) # of times in this domain sched_balance_rq() checked but found
95 7) # of times in this domain sched_balance_rq() was called but did
98 cpu was idle but no busier group was found
101 10) # of times in this domain sched_balance_rq() checked but found the
110 15) # of times in this domain sched_balance_rq() was called but did not
113 was busy but no busier group was found
117 18) # of times in this domain sched_balance_rq() checked but found the
126 23) # of times in this domain sched_balance_rq() was called but did not
[all …]
|
| D | sched-nice-design.rst | 43 This approach worked to some degree for some time, but later on with
46 a CPU utilization, but because it causes too frequent (once per
53 But the fundamental HZ-sensitive property for nice+19 still remained,
58 To sum it up: we always wanted to make nice levels more consistent, but
62 The second (less frequent but still periodically occurring) complaint
85 SCHED_FIFO. But this caused other problems: SCHED_FIFO is not starvation
|
| /Documentation/filesystems/bcachefs/ |
| D | CodingStyle.rst | 12 good. But appreciate beauty when you see it - and let people know.
33 expensive - but don't turn everything into a debug mode assertion, so that
47 means that you can run them in only a few places in the checked in version, but
53 the compiler could check. This is something that exists today, but it'll likely
54 still be a few decades before it comes to systems programming languages. But we
91 tool, but always look for more immediate ways to make things visible. When we
130 become product-manager focused. Often time an idea is a good one but needs to
131 wait for its proper time - but you won't know if it's the proper time for an
140 But don't be afraid to tackle projects that require significant rework of
178 Put effort into your documentation, commit messages, and code comments - but
[all …]
|
| /Documentation/devicetree/bindings/ |
| D | ABI.rst | 12 break on an older device tree, but that doesn't mean the binding is
18 new. These guidelines aren't new, but they desperately need to be
29 3) Bindings can be augmented, but the driver shouldn't break when given
30 the old binding. ie. add additional properties, but don't change the
|
| /Documentation/firmware-guide/acpi/ |
| D | osi.rst | 24 but where Linux was installed to replace the original OS (Windows or OSX).
27 but many were tested to run with just one specific version of Windows.
35 But Linux isn't actually compatible with Windows, and the Linux community
39 But it is likely that they will all eventually be added.
82 But _OS had fundamental problems. First, the BIOS needed to know the name
112 But two bad things happened. First, the Windows ecosystem used _OSI
113 not as designed, but as a direct replacement for _OS -- identifying
120 Linux had no choice but to also return TRUE to _OSI("Windows 2001")
132 using it in untested BIOS flows. But some OEM's used _OSI("Linux")
142 of over-stating that compatibility; but the alternative has often been
[all …]
|
| /Documentation/translations/ |
| D | index.rst | 30 documentation in their native language, but please bear in mind that the
50 Translations try to be as accurate as possible but it is not possible to map
54 translations, you may find slight differences that carry the same message but
57 If you need to communicate with the Linux community but you do not feel
|
| /Documentation/i2c/busses/ |
| D | i2c-via.rst | 28 You have VT82C586B on the motherboard, but not in the listing.
35 No error messages, but still i2c doesn't seem to work.
39 datasheets, but there are several ways the motherboard manufacturer
|
| /Documentation/maintainer/ |
| D | pull-requests.rst | 11 Mauro Carvalho Chehab. Misrepresentation was unintentional but inevitable,
60 not just make sense to me, but make sense as a historical record
68 (or even bug-fixes, but ones that look scary), explain not just
69 what they do and why they do it, but explain the _timing_. What
80 trivial formatting (the whole indentation and quoting etc), but
83 it right now), but may not make sense in the context of a merge
86 particularly for non-native speakers (but also for native ones
87 ;^). But I may miss some, or even add some.
134 will do this for you with the ``git request-pull`` command, but it needs a
148 can be used here instead as well (but note that some people behind
|
| /Documentation/admin-guide/mm/ |
| D | ksm.rst | 14 by sharing the data common between them. But it can be useful to any
26 KSM's merged pages were originally locked into kernel memory, but can now
27 be swapped out just like other user pages (but sharing is broken when they
48 with EAGAIN, but more probably arousing the Out-Of-Memory killer.
77 readable by all but writable only by root:
112 * set to 0 to stop ksmd from running but keep merged pages,
114 * set to 2 to stop ksmd and unmerge all pages currently merged, but
142 deduplication factor will be, but the slower the worst case
157 lower latency, but they will make ksmd use more CPU during the
204 how many pages unique but repeatedly checked for merging
[all …]
|
| /Documentation/w1/masters/ |
| D | ds2490.rst | 41 communication speeds, but only the normal is supported.
47 short, alarming presence on reset, and no presence on reset, but the
50 detail, but my observation is if fewer bytes are requested than are
62 the ds2490 hardware, but if the module was unloaded, then reloaded
66 show a successful completion, but the ds2490 status register would
|
| /Documentation/sound/cards/ |
| D | hdspm.rst | 33 receiver, only 56 are transmitted/received over the MADI, but
42 over the MADI, but all 32 channels are available for the mixer,
51 over the MADI, but all 16 channels are available for the mixer,
77 result), but if MMAP is used by the application. Therefore it
116 control-panel, but buffer-sizes are controlled with ALSA from
130 !!!! This is a hardware-function but is in conflict with the
151 !!!! This is no pure hardware function but was implemented by
169 card should synchronise better in MADI Mode. But since the
282 Should be "Autosync Rate", but Name used is
369 channels have to be muted on after loading the driver, but was
[all …]
|
| /Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 14 "``loadpin.enforce``". By default, it is enabled, but can be disabled at
20 a mutable filesystem means pinning is mutable too, but having the
25 included, but they can be excluded using kernel command line option such
|
| /Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 14 Normally it's the base page size of the kernel, but
18 kernel will never kill anything for this, but rather
39 Normally it's the base page size of the kernel, but
|
| /Documentation/admin-guide/media/ |
| D | cafe_ccic.rst | 17 well, but that is a debugging aid which will be removed shortly). VGA and
18 QVGA modes work; CIF is there but the colors remain funky. Only the OV7670
39 This option nails down the memory for the life of the module, but
52 will consent to work with. Default is one, but, on slower systems,
|
| /Documentation/arch/powerpc/ |
| D | pci_iov_resource_on_powernv.rst | 29 state bits (one for MMIO and one for DMA, they get set together but can be
34 captures things like the details of the error that caused the freeze etc., but
53 memory but accessed in HW by the chip) that provides a direct
91 reserved for MSIs but this is not a problem at this point; we just
106 but that would mean using a completely different address allocation
116 bits which are not conveyed by PowerBus but we don't use this.
146 mechanism to make the freeze state cascade to "companion" PEs but
149 SW. We lose a bit of effectiveness of EEH in that case, but that's
158 sense, but we haven't done it yet.
170 PCI devices, but the BARs in VF config space headers are unusual. For
[all …]
|
| /Documentation/networking/ |
| D | alias.rst | 9 address/prefixes per interface, but aliases are still supported
13 This string is usually numeric, but this is not a must.
42 Aliases are not real devices, but programs should be able to configure
|
| D | ipv6.rst | 11 or modprobe command, but are usually specified in either
22 Specifies whether to load the IPv6 module, but disable all
24 has a dependency on the IPv6 module being loaded, but no
|
| /Documentation/admin-guide/ |
| D | numastat.rst | 15 but restrictions such as mempolicies can change that, so there are also two
29 but ended up with memory from this node.
32 but ended up with memory from another node.
48 Note that on systems with memoryless nodes (where a node has CPUs but no
|
| /Documentation/driver-api/ |
| D | device-io.rst | 31 memory, but as accesses to a device. Some architectures define devices
32 to be at a fixed address, but most have some method of discovering
34 document does not cover how to receive such an address, but assumes you
154 points to a virtual memory address and can be offset or dereferenced, but in
184 each other, but contain a less expensive barrier operation. A device driver
196 identical behavior, but they can also operate on ``__iomem`` tokens returned
205 These behave in the same way as the ioread32()/iowrite32() family, but with
214 Drivers that use readl()/writel() this way are generally not portable, but
223 on 32-bit architectures but allow two consecutive 32-bit accesses instead.
237 a four-byte __raw_readl() does not get split into individual byte loads, but
[all …]
|