| /linux/tools/memory-model/litmus-tests/ |
| H A D | Z6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus | 7 * when there is but one non-reads-from (AKA non-rf) link, does not suffice
8 * if there is more than one. Of the three processes, only P1() reads from
9 * P0's write, which means that there are two non-rf links: P1() to P2()
12 * When there are two or more non-rf links, you typically will need one
|
| /linux/Documentation/locking/ |
| H A D | robust-futexes.rst | 18 that says "there's a waiter pending", and the sys_futex(FUTEX_WAIT)
23 value) that there were waiter(s) pending, and does the
26 state, and there's no in-kernel state associated with it. The kernel
27 completely forgets that there ever was a futex at that address. This
44 the kernel cannot help with the cleanup: if there is no 'futex queue'
45 (and in most cases there is none, futexes being fast lightweight locks)
75 because the kernel has no knowledge about how many robust futexes there
89 At the heart of this new approach there is a per-thread private list of
93 time, the kernel checks this user-space list: are there any robust futex
96 In the common case, at do_exit() time, there is no list registered, so
[all …]
|
| H A D | lockdep-design.rst | 152 i.e., there can be any other locking sequence between the acquire-lock
169 kernel: when acquiring a new lock, the validator checks whether there is
196 instance of the same lock-class. Such cases typically happen when there
198 cases there is an inherent "natural" ordering between the two objects
389 then there is likely a leak. The following command can be used to
439 and there is no deadlock. However, if read_lock_2() is non-recursive readers,
515 because there are 3 types for lockers, there are, in theory, 9 types of lock
525 IOW, whether there is a locker L3 that L1 blocks L3 and L2 gets blocked by L3. So
531 With the above combination for simplification, there are 4 types of dependency edges
588 If there is a closed strong path (i.e. a strong circle), then there is a
[all …]
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | nvidia,tegra-regulators-coupling.txt | 5 Thus on Tegra20 there are 3 coupled regulators and on NVIDIA Tegra30
6 there are 2.
11 On Tegra20 SoC's there are 3 coupled regulators: CORE, RTC and CPU.
18 On Tegra30 SoC's there are 2 coupled regulators: CORE and CPU. The CORE
|
| /linux/Documentation/timers/ |
| H A D | no_hz.rst | 38 there are some situations where this old-school approach is still the
40 that use short bursts of CPU, where there are very frequent idle
43 clock interrupts will normally be delivered any way because there
68 If a CPU is idle, there is little point in sending it a scheduling-clock
84 unnecessary scheduling-clock interrupts. In these situations, there
107 If a CPU has only one runnable task, there is little point in sending it
108 a scheduling-clock interrupt because there is no other task to switch to.
121 by one less than the number of CPUs. In these situations, there is
131 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
160 4. If there are more perf events pending than the hardware can
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-lefi-boardinfo | 7 and BIOS version when there exists problems related with
29 By the way, using dmidecode command can get the similar info if there
30 exists SMBIOS in firmware, but the fact is that there is no SMBIOS on
|
| H A D | sysfs-bus-i2c-devices-pca954x | 12 channel, which is useful when there is a device
19 which is useful if there is one channel that is
|
| H A D | sysfs-kernel-boot_params | 9 If there's no setup_data in boot_params the subdirectory will
19 as a link list. In "setup_data" subdirectory there's one
|
| /linux/arch/arm/vfp/ |
| H A D | vfphw.S | 40 tst r0, #FPEXC_EX @ is there additional state to restore?
43 tst r0, #FPEXC_FP2V @ is there an FPINST2 to write?
58 tst r1, #FPEXC_EX @ is there additional state to save?
61 tst r1, #FPEXC_FP2V @ is there an FPINST2 to read?
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-edid.rst | 56 pad of the subdevice. If there is no EDID support for the given ``pad``
66 If there are fewer blocks than specified, then the driver will set
67 ``blocks`` to the actual number of blocks. If there are no EDID blocks
77 there are.
81 If there are no EDID blocks available at all, then
90 The driver assumes that the full EDID is passed in. If there are more
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | apq8094-sony-xperia-kitakami-karin_windy.dts | 8 /* As the names may imply, there is quite a bunch of duplication there. */
|
| /linux/Documentation/process/ |
| H A D | 6.Followthrough.rst | 13 It is a rare patch which is so good at its first posting that there is no
40 people remember who wrote kernel code, but there is little lasting fame
101 but there are times when somebody simply has to make a decision. If you
118 things. In particular, there may be more than one tree - one, perhaps,
122 For patches applying to areas for which there is no obvious subsystem tree
131 there's a good chance that you will get more comments from a new set of
153 the patch before. It may be tempting to ignore them, since there is no
162 where there are testers, there will be bug reports.
173 After any regressions have been dealt with, there may be other, ordinary
181 And don't forget that there are other milestones which may also create bug
[all …]
|
| H A D | 3.Early-stage.rst | 131 the MAINTAINERS file for a relevant place to post. If there is a suitable
132 subsystem list, posting there is often preferable to posting on
138 and not all subsystems are represented there. The person listed in the
140 that role currently. So, when there is doubt about who to contact, a
178 matter is (1) kernel developers tend to be busy, (2) there is no shortage
186 not assume that it means there is no interest in the project.
187 Unfortunately, you also cannot assume that there are no problems with your
207 considering whether the secrecy is really necessary; there is often no real
210 That said, there are also cases where a company legitimately cannot
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-tpda.rst | 45 integration_test (by cat tmc_etf0/mgmt/rwp), it means there is data
48 There must be a tpda between tpdm and the sink. When there are some
51 there is only tpdm trace hw in the HW block, tpdm will connect to
|
| /linux/Documentation/maintainer/ |
| H A D | messy-diffstat.rst | 30 Here, there are two clear points in the history; Git will essentially
43 the mainline branch (let's call it "linus") and cN, there are still two
59 What is happening here is that there are no longer two clear end points for
63 starts at vN-rc1, it may end up including all of the changes between there
78 shame. Create a new, throwaway branch and do the merge there::
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | orphan.rst | 6 In unix there can inodes that are unlinked from directory hierarchy but that
37 RO_COMPAT_ORPHAN_PRESENT feature in the superblock to indicate there may
40 there as usual. When cleanly unmounting the filesystem we remove the
|
| H A D | special_inodes.rst | 15 - Doesn't exist; there is no inode 0.
39 Note that there are also some inodes allocated from non-reserved inode numbers
|
| /linux/drivers/gpu/drm/i915/ |
| H A D | TODO.txt | 6 improved a lot the past 2 years, there's no reason anymore not to use it.
8 - Come up with a plan what to do with drm/scheduler and how to get there.
28 maybe even remove it if there's nothing left.
|
| /linux/Documentation/ |
| H A D | Kconfig | 6 bool "Warn if there's a missing documentation file"
16 bool "Warn if there are errors at ABI files"
|
| /linux/Documentation/driver-api/media/drivers/ |
| H A D | bttv-devel.rst | 14 To handle the grabber boards correctly, there is a array tvcards[] in
27 If your card isn't listed there, you might check the source code for
28 new entries which are not listed yet. If there isn't one for your
35 module like ``msp3400`` to make sound work. If there isn't one for the
63 As mentioned above, there is a array which holds the required
|
| /linux/Documentation/power/ |
| H A D | basic-pm-debugging.rst | 49 there is the file /sys/power/pm_test that can be used to make the hibernation
109 If the "freezer" test fails, there is a task that cannot be frozen (in that case
112 that there is a problem with the tasks freezer subsystem that should be
115 If the "devices" test fails, most likely there is a driver that cannot suspend
126 Once you have found the failing driver (there can be more than just one of
136 If the "platform" test fails, there is a problem with the handling of the
162 "reboot", "shutdown" and "platform" modes. If that does not work, there
165 individually. Otherwise, there is a problem with a modular driver and you can
168 - if there are n modules loaded and the attempt to suspend and resume fails,
171 - if there are n modules loaded and the attempt to suspend and resume succeeds,
[all …]
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-async-req.rst | 48 truly non-blocking. If there is an ongoing async request it waits
50 doesn't wait for the new request to complete. If there is no ongoing
67 with the previous transfer, since there is no previous request.
69 The argument is_first_req in pre_req() indicates that there is no previous
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-opal-elog | 15 Linux if there is no room for more log entries.
38 For each log entry (directory), there are the following
48 In the future there may be additional types.
|
| /linux/Documentation/images/ |
| H A D | COPYING-logo | 2 ("currently unofficial" just means that there has been no paperwork and
7 Note that there are black-and-white versions of this available that
|
| /linux/Documentation/livepatch/ |
| H A D | livepatch.rst | 46 a live patch is called with the help of a custom ftrace handler. But there are
53 Functions are there for a reason. They take some input parameters, acquire or
64 But there are more complex fixes. For example, a patch might change
119 (Note there's not yet such an approach for kthreads.)
150 actually delivered (there is no data in signal pending structures). Tasks are
155 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
165 guaranteed there is no task sleeping in such module. It implies unbounded
176 For adding consistency model support to new architectures, there are a
180 for non-DWARF unwinders, also making sure there's a way for the stack
187 point in the loop where there are no locks taken and all data
[all …]
|