| /linux/drivers/hwtracing/coresight/ |
| H A D | coresight-etm.h | 162 * @seq_12_event: event causing the transition from 1 to 2.
163 * @seq_21_event: event causing the transition from 2 to 1.
164 * @seq_23_event: event causing the transition from 2 to 3.
165 * @seq_31_event: event causing the transition from 3 to 1.
166 * @seq_32_event: event causing the transition from 3 to 2.
167 * @seq_13_event: event causing the transition from 1 to 3.
|
| /linux/drivers/gpio/ |
| H A D | gpiolib-acpi-quirks.c | 173 * event handler on INT33FFC:02 pin 12, causing spurious wakeups.
187 * event handler on INT33FF:01 pin 0, causing spurious wakeups.
189 * keyboard is turned off, causing INT0002 ACPI events to
208 * event handler on INT33FC:02 pin 28, causing spurious wakeups.
223 * event handler on INT33FF:01 pin 0, causing spurious wakeups.
|
| /linux/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/ |
| H A D | l1d_cache.json | 67 …h shared status and requests exclusive access in the Level 1 data cache, causing a coherence acces…
71 … "This event counts demand access that misses in the Level 1 data cache, causing an access to outs…
|
| H A D | l2_cache.json | 90 …us and requests exclusive access in the Level 1 data and Level 2 caches, causing a coherence acces…
118 …counts demand access that misses in the Level 1 data and Level 2 caches, causing an access to outs…
|
| /linux/drivers/pci/hotplug/ |
| H A D | pci_hotplug_core.c | 494 * pci_hp_ignore_link_change - begin code section causing spurious link changes
497 * Mark the beginning of a code section causing spurious link changes on the
517 * pci_hp_unignore_link_change - end code section causing spurious link changes
520 * Mark the end of a code section causing spurious link changes on the
535 * Check whether a code section is executing concurrently which is causing
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a65-e1/ |
| H A D | ifu.json | 93 … moved from an active state to an inactive state (long-term sleep state, causing deallocation of s…
96 … moved from an active state to an inactive state (long-term sleep state, causing deallocation of s…
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 136 causing I/O operations to stall.
279 filesystem could be stopped, and thus causing the system
283 directory structures of unlimited depth, possibly causing a
285 resources, again causing *DoS*.
|
| /linux/include/uapi/linux/ |
| H A D | membarrier.h | 80 * but have the downside of causing extra
105 * causing extra overhead. If this command is
|
| /linux/arch/sparc/include/asm/ |
| H A D | iommu_32.h | 62 #define IOMMU_AFSR_SIZE 0x0e000000 /* Size of transaction causing error */
84 #define IOMMU_MFSR_C 0x00000800 /* Address causing error was marked cacheable */
|
| /linux/Documentation/mm/ |
| H A D | vmalloced-kernel-stacks.rst | 26 overflows to be caught immediately rather than causing difficult to
65 immediately rather than causing difficult-to-diagnose corruption.
|
| /linux/arch/arc/include/uapi/asm/ |
| H A D | setup.h | 3 * even if there's nothing to export - causing empty <uapi/asm/setup.h>
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 94 may help clean up any residual config items which could be causing problems.
97 Doing so should allow you to determine if UML is causing the issue you're
|
| /linux/include/linux/ |
| H A D | refcount_types.h | 12 * there. This avoids wrapping the counter and causing 'spurious'
|
| /linux/kernel/trace/rv/monitors/pagefault/ |
| H A D | Kconfig | 13 Monitor that real-time tasks do not raise page faults, causing
|
| /linux/arch/parisc/kernel/vdso64/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/parisc/kernel/vdso32/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/mips/dec/prom/ |
| H A D | locore.S | 27 addiu k0, 4 # skip the causing instruction
|
| /linux/include/sound/ |
| H A D | wm9090.h | 19 * potentially causing hardware damage.
|
| /linux/arch/powerpc/kernel/vdso/ |
| H A D | gen_vdso64_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| H A D | gen_vdso32_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/arch/arm64/kernel/vdso/ |
| H A D | gen_vdso_offsets.sh | 9 # causing Kbuild to rebuild the vdso-offsets header file every time.
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | struct_ops_detach.c | 12 * At some point that was causing issues due to legacy logic of treating such
|
| /linux/tools/testing/selftests/pstore/ |
| H A D | pstore_crash_test | 13 prlog "Causing kernel crash ..."
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | xe_gt_throttle.c | 33 * - ``reasons``: Array of reasons causing throttling separated by space
53 * - ``reasons``: Array of reasons causing throttling separated by space
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-regressions.rst | 88 the first broken one. Ideally try to find the exact change causing the
137 Nearly all of them are, as long as the change causing the regression (the
254 In extremely rare situations security issues can't be fixed without causing
258 issues without causing regressions.
264 What happens if fixing a regression is impossible without causing another?
|