Home
last modified time | relevance | path

Searched full:happens (Results 1 – 25 of 1616) sorted by relevance

12345678910>>...65

/Linux-v5.10/include/linux/
Dinstrumented.h19 * before the actual read happens.
34 * before the actual write happens.
49 * before the actual write happens.
64 * before the actual read happens.
79 * before the actual write happens.
94 * inserted before the actual write happens.
Dmigrate_mode.h11 * with the CPU. Instead, page copy happens outside the migratepage()
/Linux-v5.10/arch/mips/cavium-octeon/executive/
Dcvmx-interrupt-decodes.c240 /*pcs_int_en_reg.s.dup = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
245 /*pcs_int_en_reg.s.rxerr_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
250 /*pcs_int_en_reg.s.xmit_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
251 /*pcs_int_en_reg.s.lnkspd_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
255 /*pcs_int_en_reg.s.dup = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
260 /*pcs_int_en_reg.s.rxerr_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
265 /*pcs_int_en_reg.s.xmit_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
266 /*pcs_int_en_reg.s.lnkspd_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
292 pcsx_int_en_reg.s.bitlckls_en = 0; /* Happens if XAUI module is not installed */ in __cvmx_interrupt_pcsxx_int_en_reg_enable()
/Linux-v5.10/Documentation/i2c/busses/
Di2c-ali1563.rst22 notable exceptions. One of those happens to be the fact they upgraded the
23 i2c core to be SMBus 2.0 compliant, and happens to be almost identical to
/Linux-v5.10/Documentation/core-api/
Ddebug-objects.rst78 problem before the real initialization of the object happens. E.g. it
101 problem before the real initialization of the object happens. E.g. it
125 problem before the real activation of the object happens. E.g. it can
165 before the real destruction of the object happens. E.g. it can
181 object happens. E.g. it can deactivate an active object in order to
/Linux-v5.10/fs/efs/
Dfile.c24 * i have no idea why this happens as often as it does in efs_get_block()
48 * i have no idea why this happens as often as it does in efs_bmap()
/Linux-v5.10/arch/alpha/include/asm/
Dextable.h15 * Either errreg or valreg may be $31, in which case nothing happens.
17 * The exception fixup information "just so happens" to be arranged
/Linux-v5.10/mm/
Dmaccess.c97 * fault happens, handle that and return -EFAULT. If @src is not a valid kernel
133 * happens, handle that and return -EFAULT.
203 * happens, handle that and return -EFAULT.
230 * happens, handle that and return -EFAULT.
/Linux-v5.10/tools/testing/selftests/powerpc/signal/
Dsignal_tm.c62 * If anything bad happens in ASM and we fail to set ret in test_signal_tm()
77 * happens. in test_signal_tm()
/Linux-v5.10/arch/c6x/lib/
Dstrasgi.S61 ;; loop back branch happens here
76 ;; return happens here
/Linux-v5.10/Documentation/PCI/
Dpcieaer-howto.rst154 fatal error happens. The root port aer service driver provides a
244 What happens if a PCI Express device driver does not provide an
253 What happens if an upstream port service driver does not provide
266 driver when an error happens. But if the driver is not aware of
/Linux-v5.10/Documentation/timers/
Dhighres.rst161 calls when an interrupt happens. The overhead would be much larger than the
174 When the timer interrupt happens, the next event interrupt handler is called
224 called when an interrupt happens during the idle period, which does not cause a
233 hrtimer_update_jiffies() is called from irq_enter() when an interrupt happens
/Linux-v5.10/security/
Dinode.c100 * file is to be removed (no automatic cleanup happens if your module
193 * to be removed (no automatic cleanup happens if your module is unloaded,
221 * to be removed (no automatic cleanup happens if your module is unloaded,
253 * to be removed (no automatic cleanup happens if your module is unloaded,
/Linux-v5.10/drivers/staging/fieldbus/Documentation/
Dfieldbus_dev.txt25 Communication between PLC and device typically happens via process data memory,
47 Registration then happens by calling fieldbus_dev_register().
/Linux-v5.10/fs/btrfs/
Dacl.c81 * allocation context to avoid deadlock if reclaim happens. in __btrfs_set_acl()
132 /* this happens with subvols */ in btrfs_init_acl()
/Linux-v5.10/arch/powerpc/platforms/embedded6xx/
Dlinkstation.c112 for(;;) /* Spin until reset happens */ in linkstation_restart()
125 for(;;) /* Spin until power-off happens */ in linkstation_power_off()
/Linux-v5.10/drivers/oprofile/
Devent_buffer.c68 /* Wake up the waiting process if any. This happens
134 /* NB: the actual start happens from userspace in event_buffer_open()
/Linux-v5.10/kernel/
Dextable.c129 * If a stack dump happens while RCU is not watching, then in kernel_text_address()
132 * triggers a stack trace, or a WARN() that happens during in kernel_text_address()
/Linux-v5.10/Documentation/bpf/
Dprog_cgroup_sysctl.rst72 written to sysctl before actual write happens. This helper can be used only
76 written to sysctl before actual write happens. Sysctl value will be
/Linux-v5.10/Documentation/process/
Dvolatile-considered-harmful.rst69 hyperthreaded twin processor; it also happens to serve as a compiler
79 ensures that the access happens as expected by the programmer.
/Linux-v5.10/net/rds/
Dib_ring.c44 * Freeing always happens in an interrupt, and hence only
62 * This only happens on shutdown.
/Linux-v5.10/drivers/net/wireless/intel/ipw2x00/
DKconfig35 initialization time, and when built-in this typically happens
97 initialization time, and when built-in this typically happens
/Linux-v5.10/Documentation/locking/
Drobust-futexes.rst92 registration happens at most once per thread lifetime]. At do_exit()
139 - no per-lock kernel allocation happens.
187 thread lifetime, and the cleanup operation, if it happens, is fast and
/Linux-v5.10/Documentation/dev-tools/
Dkcsan.rst305 KTSAN is a happens-before data race detector, which explicitly establishes the
306 happens-before order between memory operations, which can then be used to
309 To build a correct happens-before relation, KTSAN must be aware of all ordering
313 mechanisms. To track the happens-before relation, KTSAN's implementation
/Linux-v5.10/drivers/gpu/drm/msm/dp/
Ddp_catalog.c77 * To make sure aux reg writes happens before any other operation, in dp_write_aux()
94 * To make sure phy reg writes happens before any other operation, in dp_write_ahb()
105 * To make sure interface reg writes happens before any other operation, in dp_write_p0()
116 * To make sure interface reg writes happens before any other operation, in dp_read_p0()
133 * To make sure link reg writes happens before any other operation, in dp_write_link()
357 * To make sure link reg writes happens before other operation, in dp_catalog_ctrl_mainlink_ctrl()

12345678910>>...65