| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/ |
| D | pipeline.json | 9 …rontend, cache miss.This event counts every cycle the DPU IQ is empty and there is an instruction …
12 …rontend, cache miss.This event counts every cycle the DPU IQ is empty and there is an instruction …
15 … frontend, TLB miss.This event counts every cycle the DPU IQ is empty and there is an instruction …
18 … frontend, TLB miss.This event counts every cycle the DPU IQ is empty and there is an instruction …
21 …d, pre-decode error.This event counts every cycle the DPU IQ is empty and there is a pre-decode er…
24 …d, pre-decode error.This event counts every cycle the DPU IQ is empty and there is a pre-decode er…
27 …backend interlock.This event counts every cycle that issue is stalled and there is an interlock. S…
30 …backend interlock.This event counts every cycle that issue is stalled and there is an interlock. S…
33 …d, interlock, AGU.This event counts every cycle that issue is stalled and there is an interlock th…
36 …d, interlock, AGU.This event counts every cycle that issue is stalled and there is an interlock th…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/cortex-a510/ |
| D | pipeline.json | 21 … cycle that the Data Processing Unit (DPU) instruction queue is empty and there is an instruction …
24 … cycle that the Data Processing Unit (DPU) instruction queue is empty and there is an instruction …
27 …This event counts every cycle that the DPU instruction queue is empty and there is an instruction …
30 …This event counts every cycle that the DPU instruction queue is empty and there is an instruction …
39 …s event counts every cycle where the issue of an operation is stalled and there is an interlock. S…
42 …s event counts every cycle where the issue of an operation is stalled and there is an interlock. S…
45 …s event counts every cycle where the issue of an operation is stalled and there is an interlock on…
48 …s event counts every cycle where the issue of an operation is stalled and there is an interlock on…
51 … or the Vector Processing Unit (VPU). This event counts every cycle where there is a stall or an i…
54 … or the Vector Processing Unit (VPU). This event counts every cycle where there is a stall or an i…
[all …]
|
| /kernel/linux/linux-6.6/include/linux/atomic/ |
| D | atomic-instrumented.h | 25 * Unsafe to use in noinstr code; use raw_atomic_read() there.
42 * Unsafe to use in noinstr code; use raw_atomic_read_acquire() there.
60 * Unsafe to use in noinstr code; use raw_atomic_set() there.
78 * Unsafe to use in noinstr code; use raw_atomic_set_release() there.
97 * Unsafe to use in noinstr code; use raw_atomic_add() there.
115 * Unsafe to use in noinstr code; use raw_atomic_add_return() there.
134 * Unsafe to use in noinstr code; use raw_atomic_add_return_acquire() there.
152 * Unsafe to use in noinstr code; use raw_atomic_add_return_release() there.
171 * Unsafe to use in noinstr code; use raw_atomic_add_return_relaxed() there.
189 * Unsafe to use in noinstr code; use raw_atomic_fetch_add() there.
[all …]
|
| /kernel/linux/linux-6.6/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/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-6.6/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-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-6.6/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
84 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/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-6.6/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-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-6.6/Documentation/livepatch/ |
| D | livepatch.rst | 15 There are many situations where users are reluctant to reboot a system. It may
26 There are multiple mechanisms in the Linux kernel that are directly related
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, get or
64 But there are more complex fixes. For example, a patch might change
80 switching combined with kpatch's stack trace switching. There are also
119 (Note there's not yet such an approach for kthreads.)
142 There's also a /proc/<pid>/patch_state file which can be used to
150 actually delivered (there is no data in signal pending structures). Tasks are
155 /sys/kernel/livepatch/<patch>/force attribute. Writing 1 there clears
[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-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 …]
|
| /kernel/linux/linux-6.6/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
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
151 To begin with, the visibility of your patch has increased yet again. There
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
[all …]
|
| /kernel/linux/linux-5.10/include/net/netfilter/ |
| D | nf_tproxy.h | 46 * redirect the new connection to the proxy if there's a listener
51 * Returns the listener socket if there's one, the TIME_WAIT socket if
63 * - match: if there's a fully established connection matching the
68 * - match: if there's a listening socket matching the redirection
71 * address. The reasoning is that if there's an explicit rule, it
76 * Please note that there's an overlap between what a TPROXY target
105 * redirect the new connection to the proxy if there's a listener
110 * Returns the listener socket if there's one, the TIME_WAIT socket if
|
| /kernel/linux/linux-6.6/include/net/netfilter/ |
| D | nf_tproxy.h | 46 * redirect the new connection to the proxy if there's a listener
51 * Returns the listener socket if there's one, the TIME_WAIT socket if
63 * - match: if there's a fully established connection matching the
68 * - match: if there's a listening socket matching the redirection
71 * address. The reasoning is that if there's an explicit rule, it
76 * Please note that there's an overlap between what a TPROXY target
105 * redirect the new connection to the proxy if there's a listener
110 * Returns the listener socket if there's one, the TIME_WAIT socket if
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/broadwellde/ |
| D | uncore-power.json | 14 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
22 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
30 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
38 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
46 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
54 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
62 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
70 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
78 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
86 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/broadwellx/ |
| D | uncore-power.json | 14 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
22 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
30 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
38 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
46 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
54 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
62 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
70 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
78 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
86 …"PublicDescription": "Number of cycles spent performing core C state transitions. There is one ev…
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/ |
| D | tlb.json | 4 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
8 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
36 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
40 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| D | tlb.json | 4 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
8 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
36 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
40 …there are multiple misses in the TLB that are resolved by the refill, then this event only counts …
|
| /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-6.6/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-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
|