Home
last modified time | relevance | path

Searched refs:catch (Results 1 – 25 of 50) sorted by relevance

12

/Linux-v5.4/drivers/gpu/drm/i915/
DKconfig.debug42 performance but will catch some internal issues.
120 performance but will catch some internal issues.
132 performance but will catch some internal issues.
/Linux-v5.4/arch/xtensa/
DKconfig.debug31 It is easy to make wrong hardware configuration, this test should catch it early.
/Linux-v5.4/Documentation/dev-tools/
Dubsan.rst6 UBSAN uses compile-time instrumentation to catch undefined behavior (UB).
/Linux-v5.4/Documentation/trace/
Dstm.rst70 catch-all entry "default" will be used, if it exists. This entry also
115 node, the stm core will use the catch-all entry "default", if one
Dmmiotrace.rst67 Load the driver you want to trace and use it. Mmiotrace will only catch MMIO
/Linux-v5.4/Documentation/networking/device_drivers/toshiba/
Dspider_net.txt56 flowing, then the tail pointer can catch up to the hardware pointer.
68 RX traffic is flowing, then the head pointer can catch up to the tail
117 pointer will catch up to the head, notice the not-empty condition,
/Linux-v5.4/Documentation/x86/
Dintel-iommu.rst52 We also allocate guard pages with each mapping, so we can attempt to catch
Dkernel-stacks.rst98 the IST stackpointer to a guard hole to catch triple nesting.
/Linux-v5.4/fs/proc/
Darray.c252 sigset_t *catch) in collect_sigign_sigcatch() argument
262 sigaddset(catch, i); in collect_sigign_sigcatch()
/Linux-v5.4/drivers/nvdimm/
DKconfig129 otherwise helps catch build errors induced by changes to the
/Linux-v5.4/kernel/dma/
DKconfig166 This also attempts to catch cases where a page owned by DMA is
/Linux-v5.4/Documentation/PCI/
Dacpi-info.rst66 bridge registers (including ECAM space) in PNP0C02 catch-all devices [6].
78 PNP0C02 "motherboard" devices are basically a catch-all.  There's no
/Linux-v5.4/Documentation/filesystems/
Dxfs-self-describing-metadata.txt155 As such, we cannot catch all types of corruption that can occur within a block
165 marks the object being read as EFSCORRUPTED. The caller needs to catch this
183 error for the higher layers to catch.
/Linux-v5.4/Documentation/bpf/
Dprog_cgroup_sysctl.rst106 environment, for example to monitor sysctl usage or catch unreasonable values
/Linux-v5.4/Documentation/scheduler/
Dsched-domains.rst82 which should catch most possible errors (described above). It also prints out
/Linux-v5.4/Documentation/locking/
Dww-mutex-design.rst67 to catch w/w mutex interface abuse. An acquire context is representing a
262 objects acquired with the fixed list. But the w/w mutex debug checks will catch
/Linux-v5.4/Documentation/process/
D4.Coding.rst228 of us can reach. What we can hope to do, though, is to catch and fix as
231 array of tools which can catch a wide variety of obscure problems in an
407 The other catch is that a developer who changes an internal API is
/Linux-v5.4/Documentation/driver-api/
Dpps.rst201 Sometimes one needs to be able not only to catch PPS signals but to produce
/Linux-v5.4/arch/powerpc/
DKconfig.debug72 This tries to catch incorrect usage of cpu_has_feature() and
/Linux-v5.4/Documentation/driver-api/thermal/
Dintel_powerclamp.rst243 may take an additional period for the rest of the CPUs to catch up
/Linux-v5.4/Documentation/vm/
Dpage_migration.rst231 (Look at __ClearPageMovable). But __PageMovable is cheap to catch whether
/Linux-v5.4/Documentation/admin-guide/blockdev/
Dzram.rst390 zram block. It could be useful to catch cold or incompressible
/Linux-v5.4/Documentation/security/
Dself-protection.rst171 hole at the bottom of the stack to catch these overflows.
/Linux-v5.4/Documentation/target/
Dtcmu-design.rst356 /* Process events from cmd ring until we catch up with cmd_head */
/Linux-v5.4/Documentation/networking/dsa/
Dsja1105.rst282 The catch is that the delay lines need to lock onto a clock signal with a

12