| /kernel/linux/linux-5.10/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"
|
| /kernel/linux/linux-4.19/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"
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/ |
| D | TODO | 5 V4L2 driver, there are still some issues preventing it to
16 There are some hacks added there for it to wait for sensors to be
26 4. There's a problem at the sensor drivers: when trying to set a video
40 5. There are several issues related to memory management, causing
56 The code there is really dirty, ugly and probably wrong. I fixed
57 one bug there already, but the best would be to just trash it and use
66 6. There is some issues at the frame receive logic, causing the
73 CHT version. Yet, there are some ISP-specific headers that change the
106 there are any specific things that can be done to fold in support for
120 for this driver until the other work is done, as there will be a lot
[all …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| 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
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 …]
|
| /kernel/linux/linux-4.19/Documentation/timers/ |
| D | NO_HZ.txt | 10 There are three main ways of managing scheduling-clock interrupts
35 there are some situations where this old-school approach is still the
37 that use short bursts of CPU, where there are very frequent idle
40 clock interrupts will normally be delivered any way because there
64 If a CPU is idle, there is little point in sending it a scheduling-clock
76 unnecessary scheduling-clock interrupts. In these situations, there
94 There is also a boot parameter "nohz=" that can be used to disable
102 If a CPU has only one runnable task, there is little point in sending it
103 a scheduling-clock interrupt because there is no other task to switch to.
116 by one less than the number of CPUs. In these situations, there is
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/arch/mips/vdso/ |
| D | vgettimeofday.c | 23 * This is behind the ifdef so that we don't provide the symbol when there's no
24 * possibility of there being a usable clocksource, because there's nothing we
59 * This is behind the ifdef so that we don't provide the symbol when there's no
60 * possibility of there being a usable clocksource, because there's nothing we
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/livepatch/ |
| D | livepatch.txt | 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
164 tasks. No proper signal is actually delivered (there is no data in signal
169 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
[all …]
|
| /kernel/linux/linux-5.10/Documentation/networking/device_drivers/ethernet/toshiba/ |
| D | spider_net.rst | 28 There are three primary states that a descriptor can be in: "empty",
46 marks it full, and advances the GDACTDPA by one. Thus, when there is
55 and advance the tail pointer. Thus, when there is flowing RX traffic,
67 then mark the descr as "empty", ready to receive data. Thus, when there
117 the hardware can fill them, there is no problem. If, for some reason,
136 and is filling the next descrs. Since the OS doesn't see this, there
157 marked xa... which is "empty". Thus, from the OS point of view, there
158 is nothing to be done. In particular, there is the implicit assumption
168 and there can be no forward progress; the OS thinks there's nothing
177 operations there. Since this will leave "holes" in the ring, there
[all …]
|
| /kernel/linux/linux-4.19/Documentation/networking/ |
| 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 …]
|
| /kernel/linux/linux-4.19/drivers/media/platform/davinci/ |
| D | Kconfig | 14 To compile this driver as a module, choose M here. There will
29 To compile this driver as a module, choose M here. There will
45 To compile this driver as a module, choose M here. There will
61 To compile this driver as a module, choose M here. There will
75 To compile this driver as a module, choose M here. There will
89 To compile this driver as a module, choose M here. There will
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | basic-pm-debugging.txt | 43 there is the file /sys/power/pm_test that can be used to make the hibernation
44 core run in a test mode. There are 5 test modes available:
101 If the "freezer" test fails, there is a task that cannot be frozen (in that case
104 that there is a problem with the tasks freezer subsystem that should be
107 If the "devices" test fails, most likely there is a driver that cannot suspend
117 Once you have found the failing driver (there can be more than just one of
127 If the "platform" test fails, there is a problem with the handling of the
152 "reboot", "shutdown" and "platform" modes. If that does not work, there
155 individually. Otherwise, there is a problem with a modular driver and you can
158 - if there are n modules loaded and the attempt to suspend and resume fails,
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-4.19/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 20 There is thus, in HW, a table of PE states that contains a pair of "frozen"
25 return all 1's value. MSIs are also blocked. There's a bit more state that
57 bridge being triggered. There's a PE# in the interrupt controller
66 from the CPU address space to the PCI address space. There is one M32
83 need to ensure Linux doesn't assign anything there, the M32 logic
106 address on the PowerBus). There is a way to also set the top 14
111 has 256 segments; however, there is no table for mapping a segment
115 there's a defined ordering for which window applies.
136 than one segment, we end up with more than one PE#. There is a HW
176 There are several strategies for isolating VFs in PEs:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/gpu/ |
| D | todo.rst | 56 There is a conversion guide for atomic and all you need is a GPU for a
83 now, but there's still a pile of existing drivers that easily could be
109 so there's some book-keeping involved. There's also some good fun involved in
121 a bit too severe. So there's some follow-up work to adjust the function
134 implement the userspace ABI. And then there's the optional hooks for the
137 ``_helper_funcs`` since they are not part of the core ABI. There's a
140 * There's a new helper ``drm_atomic_helper_best_encoder()`` which could be
159 and there's a ``gem_free_object_unlocked`` callback for any drivers which are
277 See https://dri.freedesktop.org/docs/drm/ for what's there already.
288 Unfortunately there's still large piles of legacy code around which needs to
[all …]
|