| /Linux-v5.4/tools/perf/pmu-events/arch/arm64/arm/cortex-a53/ |
| D | pipeline.json | 15 …"BriefDescription": "Cycles the DPU IQ is empty and there is an instruction cache miss being proce…
20 …"BriefDescription": "Cycles the DPU IQ is empty and there is an instruction micro-TLB miss being p…
25 "BriefDescription": "Cycles the DPU IQ is empty and there is a pre-decode error being processed"
30 …"BriefDescription": "Cycles there is an interlock other than Advanced SIMD/Floating-point instruc…
35 …"BriefDescription": "Cycles there is an interlock for a load/store instruction waiting for data to…
40 … "BriefDescription": "Cycles there is an interlock for an Advanced SIMD/Floating-point operation."
45 "BriefDescription": "Cycles there is a stall in the Wr stage because of a load miss"
50 "BriefDescription": "Cycles there is a stall in the Wr stage because of a store"
|
| /Linux-v5.4/Documentation/ |
| D | robust-futexes.txt | 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
42 There is a big conceptual problem with futex based mutexes though: it is
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
[all …]
|
| /Linux-v5.4/Documentation/timers/ |
| D | no_hz.rst | 12 There are three main ways of managing scheduling-clock interrupts
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
80 unnecessary scheduling-clock interrupts. In these situations, there
98 There is also a boot parameter "nohz=" that can be used to disable
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
[all …]
|
| /Linux-v5.4/include/net/netfilter/ |
| D | nf_tproxy.h | 39 * redirect the new connection to the proxy if there's a listener
44 * Returns the listener socket if there's one, the TIME_WAIT socket if
56 * - match: if there's a fully established connection matching the
61 * - match: if there's a listening socket matching the redirection
64 * address. The reasoning is that if there's an explicit rule, it
69 * Please note that there's an overlap between what a TPROXY target
98 * redirect the new connection to the proxy if there's a listener
103 * Returns the listener socket if there's one, the TIME_WAIT socket if
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | livepatch.rst | 28 There are many situations where users are reluctant to reboot a system. It may
39 There are multiple mechanisms in the Linux kernel that are directly related
59 a live patch is called with the help of a custom ftrace handler. But there are
66 Functions are there for a reason. They take some input parameters, get or
77 But there are more complex fixes. For example, a patch might change
93 switching combined with kpatch's stack trace switching. There are also
132 (Note there's not yet such an approach for kthreads.)
155 There's also a /proc/<pid>/patch_state file which can be used to
163 actually delivered (there is no data in signal pending structures). Tasks are
168 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
[all …]
|
| /Linux-v5.4/Documentation/process/ |
| 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
94 but there are times when somebody simply has to make a decision. If you
111 things. In particular, there may be more than one tree - one, perhaps,
115 For patches applying to areas for which there is no obvious subsystem tree
124 there's a good chance that you will get more comments from a new set of
144 To begin with, the visibility of your patch has increased yet again. There
146 the patch before. It may be tempting to ignore them, since there is no
155 where there are testers, there will be bug reports.
166 After any regressions have been dealt with, there may be other, ordinary
[all …]
|
| D | 3.Early-stage.rst | 44 There are a number of very good Linux kernel developers, but they
87 - There may be elements of the proposed solution which will not be
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
157 copies of the patch. There are a number of options regulating how hard
177 matter is (1) kernel developers tend to be busy, (2) there is no shortage
185 not assume that it means there is no interest in the project.
186 Unfortunately, you also cannot assume that there are no problems with your
[all …]
|
| D | 1.Intro.rst | 11 encounter there. There are a great many reasons why kernel code should be
19 the patch development, review, and merging cycle are covered. There is some
29 patches are covered, and there is an introduction to some of the tools
91 intimidating to new developers, but there are good reasons and solid
99 frustrating experience. There is a lot of material here, but the effort
134 enable it. There is no need for driver disks, downloads, or the hassles
189 There are, however, additional factors which should be taken into account
201 is there regardless.
247 the licensing of the kernel is doomed to almost certain failure. There are
250 there is no prospect of a migration to version 3 of the GPL in the
[all …]
|
| /Linux-v5.4/Documentation/networking/device_drivers/toshiba/ |
| D | spider_net.txt | 26 There are three primary states that a descriptor can be in: "empty",
44 marks it full, and advances the GDACTDPA by one. Thus, when there is
53 and advance the tail pointer. Thus, when there is flowing RX traffic,
65 then mark the descr as "empty", ready to receive data. Thus, when there
115 the hardware can fill them, there is no problem. If, for some reason,
134 and is filling the next descrs. Since the OS doesn't see this, there
155 marked xa... which is "empty". Thus, from the OS point of view, there
156 is nothing to be done. In particular, there is the implicit assumption
166 and there can be no forward progress; the OS thinks there's nothing
175 operations there. Since this will leave "holes" in the ring, there
[all …]
|
| /Linux-v5.4/Documentation/gpu/ |
| D | todo.rst | 18 implementation (there's lots of outdated locking leftovers in various
31 There is a conversion guide for atomic and all you need is a GPU for a
58 now, but there's still a pile of existing drivers that easily could be
72 a bit too severe. So there's some follow-up work to adjust the function
86 implement the userspace ABI. And then there's the optional hooks for the
89 ``_helper_funcs`` since they are not part of the core ABI. There's a
104 and there's a ``gem_free_object_unlocked`` callback for any drivers which are
137 drm_mode_config_helper_suspend/resume(). Also there's still open-coded version
165 There's drm_gem_prime_mmap() for this now, but still needs to be rolled out.
267 in the future. If there is any debug code using drm_display_mode.hsync, convert
[all …]
|
| /Linux-v5.4/drivers/media/platform/davinci/ |
| D | Kconfig | 15 To compile this driver as a module, choose M here. There will
30 To compile this driver as a module, choose M here. There will
46 To compile this driver as a module, choose M here. There will
62 To compile this driver as a module, choose M here. There will
76 To compile this driver as a module, choose M here. There will
90 To compile this driver as a module, choose M here. There will
|
| /Linux-v5.4/drivers/net/wimax/i2400m/ |
| D | tx.c | 73 * So the concepts to keep in mind there are:
96 * - If we are going to append and there is no more space (we are at
99 * beginning of the FIFO (if there is space) and append the message
100 * there.
137 * payload, we always make sure there is also free space for this
273 * at the end there are less, we pad up to the nearest
316 * buffer) if there is no head room. In this case, tail_room would be
342 * @padding: ensure that there is at least this many bytes of free
349 * calling this routine with try_head = 0. In case if there
350 * is not enough tail room space but there is enough head room space,
[all …]
|
| /Linux-v5.4/arch/x86/kvm/ |
| D | irq.c | 19 * check if there are pending timer events
32 * check if there is a pending userspace external interrupt
40 * check if there is pending interrupt from
57 * check if there is injectable interrupt:
68 * on interrupt.injected to know if there is a pending in kvm_cpu_has_injectable_intr()
88 * check if there is pending interrupt without
97 * on interrupt.injected to know if there is a pending in kvm_cpu_has_interrupt()
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ext2.txt | 8 filesystem in use by Linux. There are also implementations available
76 separate patches). There is also a versioning mechanism to allow new
128 If the filesystem is revision 1 or higher, then there are extra fields,
148 There are some reserved fields which are currently unused in the inode
159 There are pointers to the first 12 blocks which contain the file's data
160 in the inode. There is a pointer to an indirect block (which contains
168 behaviour on a per-file basis. There are flags for secure deletion,
211 In ext2, there is a mechanism for reserving a certain number of blocks
237 revision 1. There are three 32-bit fields, one for compatible features
294 If you're exceptionally paranoid, there are 3 ways of making metadata
[all …]
|
| D | debugfs.txt | 7 there. The debugfs filesystem is also intended to not serve as a stable
8 ABI to user space; in theory, there are no stability constraints placed on
9 files exported there. The real world is not always so simple, though [1];
96 architectures, though, complicating the situation somewhat. There is a
138 can be used to export binary information, but there does not appear to be
180 There is a helper function to create device related seq_file:
192 There are a couple of other directory-oriented helper functions:
208 There is one important thing that all debugfs users must take into account:
209 there is no automatic cleanup of any directories created in debugfs. If a
213 be prepared to remove all files and directories they create there. A file
|
| /Linux-v5.4/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.rst | 28 There is thus, in HW, a table of PE states that contains a pair of "frozen"
33 return all 1's value. MSIs are also blocked. There's a bit more state that
66 bridge being triggered. There's a PE# in the interrupt controller
75 from the CPU address space to the PCI address space. There is one M32
92 need to ensure Linux doesn't assign anything there, the M32 logic
115 address on the PowerBus). There is a way to also set the top 14
120 has 256 segments; however, there is no table for mapping a segment
124 there's a defined ordering for which window applies.
145 than one segment, we end up with more than one PE#. There is a HW
186 There are several strategies for isolating VFs in PEs:
[all …]
|
| /Linux-v5.4/Documentation/core-api/ |
| D | workqueue.rst | 13 There are many cases where an asynchronous process execution context
22 While there are work items on the workqueue the worker executes the
24 there is no work item left on the workqueue the worker becomes idle.
89 There are two worker-pools, one for normal work items and the other
121 stalling should be optimal. As long as there are one or more runnable
124 schedules a new worker so that the CPU doesn't sit idle while there
136 regulating concurrency level is on the users. There is also a flag to
156 also used as the name of the rescuer thread if there is one.
241 may queue at the same time. Unless there is a specific need for
332 there is dependency among multiple work items used during memory
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/rc/ |
| D | rc-protos.rst | 34 This IR protocol uses manchester encoding to encode 14 bits. There is a
79 There is a variant of rc5 called either rc5x or extended rc5
80 where there the second stop bit is the 6th commmand bit, but inverted.
83 done to keep it compatible with plain rc-5 where there are two start bits.
193 The sony protocol is a pulse-width encoding. There are three variants,
220 The sony protocol is a pulse-width encoding. There are three variants,
247 The sony protocol is a pulse-width encoding. There are three variants,
358 The scancode is the exact 16 bits as in the protocol. There is also a
367 as in the protocol. There is also a toggle bit.
375 as in the protocol. There is also a toggle bit.
[all …]
|
| /Linux-v5.4/Documentation/power/ |
| D | basic-pm-debugging.rst | 49 there is the file /sys/power/pm_test that can be used to make the hibernation
50 core run in a test mode. There are 5 test modes available:
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,
[all …]
|
| /Linux-v5.4/drivers/gpu/drm/amd/display/ |
| D | TODO | 18 "Is there any major reason to keep all those abstractions?
22 I haven't looked recently but I didn't get the impression there was a
50 subsystems, since there's really no good reason to have 2nd
52 and edid parsing. There's still a bit a midlayer feeling to the edid
79 callbacks. There's also plans to expose this stuff in a standard way across all
87 17. There's still a pretty massive layer cake around dp aux and DPCD handling,
93 18. There's a pile of sink handling code, both for DP and HDMI where I didn't
|
| /Linux-v5.4/Documentation/hid/ |
| D | uhid.rst | 7 relies heavily on the definitions declared there.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
44 The "type" field defines the payload. For each type, there is a
55 followed by an UHID_OPEN event again and so on. There is no need to perform
96 This destroys the internal HID device. No further I/O will be accepted. There
99 You can create a new device by sending UHID_CREATE2 again. There is no need to
158 there is actually no other process that reads your data so there is no need to
162 This is sent when there are no more processes which read the HID data. It is
175 The kernel serializes GET_REPORT requests so there will never be two in
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Transition-notes | 5 under ps_spinlock. There are three places where that can happen:
50 be preempted there.
51 2) When there is such a thread, pd_busy is set or pd_lock is held by
53 3) When there is such a thread, ps_tq_active is 0 or ps_spinlock is
55 4) When there is such a thread, all PIA belonging to pd.c have NULL
60 (1) can become not true if some thread enters that area while another is there.
72 case that needs consideration is call from pi_wake_up() and there
123 We don't need to reset it to NULL, since we are guaranteed that there
|
| /Linux-v5.4/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.txt | 27 | gals-rx There may be GALS in some larbs.
38 | | |... | | | ... There are different ports in each larb.
49 like display, video decode, and camera. And there are different ports
50 in each larb. Take a example, There are many ports like MC, PP, VLD in the
52 In some SoCs, there may be a GALS(Global Async Local Sync) module between
73 if there is no this "bclk".
|
| /Linux-v5.4/tools/memory-model/litmus-tests/ |
| 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-v5.4/Documentation/sound/cards/ |
| D | cmipci.rst | 12 channels can be used for front/rear playbacks. Since there are two
20 There are slight differences between the two DACs:
47 time.. Maybe there is an unknown register to achieve this...
50 playback should be routed there as default. If not, there is a
55 There are two more controls regarding to the rear output.
94 There are some control switches affecting to the speaker connections:
150 Additionally there are relevant control switches:
214 There are Master, PCM, Synth, CD, Line, Mic and PC Speaker playback
238 There is *no* hardware wavetable function on this chip (except for
|
