Home
last modified time | relevance | path

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

12345678910>>...88

/openbmc/linux/include/linux/
H A Dinstrumented.h22 * before the actual read happens.
36 * before the actual write happens.
50 * before the actual write happens.
64 * before the actual read happens.
78 * before the actual write happens.
92 * inserted before the actual write happens.
155 * whether the instrumentation happens before or after the data is copied from
173 * whether the instrumentation happens before or after the data is copied from
/openbmc/linux/arch/mips/cavium-octeon/executive/
H A Dcvmx-interrupt-decodes.c244 /*pcs_int_en_reg.s.dup = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
249 /*pcs_int_en_reg.s.rxerr_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
254 /*pcs_int_en_reg.s.xmit_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
255 /*pcs_int_en_reg.s.lnkspd_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
259 /*pcs_int_en_reg.s.dup = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
264 /*pcs_int_en_reg.s.rxerr_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
269 /*pcs_int_en_reg.s.xmit_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
270 /*pcs_int_en_reg.s.lnkspd_en = 1; // This happens during normal operation */ in __cvmx_interrupt_pcsx_intx_en_reg_enable()
297 pcsx_int_en_reg.s.bitlckls_en = 0; /* Happens if XAUI module is not installed */ in __cvmx_interrupt_pcsxx_int_en_reg_enable()
/openbmc/u-boot/include/
H A Dbouncebuf.h17 * requiring the aligned transfer happens, then the bounce buffer is lost upon
24 * operation requiring the aligned transfer happens, then the bounce buffer is
33 * requiring the aligned transfer happens, then the bounce buffer is copied
/openbmc/linux/Documentation/i2c/busses/
H A 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
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-devices-state_synced19 which happens only when all its consumer devices are registered
26 sync_state() call happens independent of the state of the
/openbmc/linux/drivers/watchdog/
H A Dmarvell_gti_wdt.c18 * This will generate the interrupt to arm core whenever timeout happens.
21 * This will generate interrupt to arm core on 1st timeout happens
22 * This will generate interrupt to SCP processor on 2nd timeout happens
25 * This will generate interrupt to arm core on 1st timeout happens
26 * Will generate interrupt to SCP processor on 2nd timeout happens,
/openbmc/linux/Documentation/core-api/
H A 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
/openbmc/linux/fs/efs/
H A 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()
/openbmc/linux/arch/alpha/include/asm/
H A 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
/openbmc/qemu/docs/system/devices/
H A Dcanokey.rst34 inspect what happens inside a secure key
42 they can see what happens inside the secure key
113 If you want to trace what happens inside the secure key, when compiling
/openbmc/linux/arch/parisc/include/asm/
H A Dextable.h14 * receive -EFAULT when an exception happens if the lowest bit in
18 * modified at runtime if a fault happens. Register %r0 will be ignored.
/openbmc/linux/Documentation/trace/
H A Dosnoise-tracer.rst36 events. When a noise happens without any interference from the operating
104 higher than the configured value happens. Writing 0 disables this
107 higher than the configured value happens. Writing 0 disables this
171 The reason roots in the overhead of the entry and exit code that happens
/openbmc/u-boot/drivers/i2c/
H A Di2c-uclass-compat.c101 /* Nothing to do here - the init happens through driver model */ in i2c_init()
106 /* Nothing to do here - the init happens through driver model */ in board_i2c_init()
/openbmc/linux/tools/testing/selftests/powerpc/signal/
H A Dsignal_tm.c63 * If anything bad happens in ASM and we fail to set ret in test_signal_tm()
78 * happens. in test_signal_tm()
/openbmc/sdbusplus/test/
H A Dtimer.cpp135 // 2 because of one more count that happens prior to exiting in TEST_F()
205 // 2 because of one more count that happens prior to exiting in TEST_F()
261 // 2 because of one more count that happens prior to exiting in TEST_F()
/openbmc/linux/tools/memory-model/Documentation/
H A Dglossary.txt40 See also "Happens-Before", "Reads-From", "Relaxed", and "Release".
123 Happens-Before (hb): A relation between two accesses in which LKMM
125 detail, please see the "THE HAPPENS-BEFORE RELATION: hb"
/openbmc/linux/security/
H A 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,
/openbmc/linux/Documentation/timers/
H A 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
/openbmc/linux/tools/testing/selftests/bpf/verifier/
H A Datomic_fetch_add.c66 /* It happens that the address leak check is first, but it would also be
79 /* It happens that the address leak check is first, but it would also be
/openbmc/linux/drivers/staging/fieldbus/Documentation/
H A Dfieldbus_dev.txt25 Communication between PLC and device typically happens via process data memory,
47 Registration then happens by calling fieldbus_dev_register().
/openbmc/qemu/python/tests/
H A Dprotocol.py83 will be similar to what happens with an unhandled Exception in
338 Test what happens when a connection attempt is aborted.
359 Test what happens when a connection attempt times out.
379 Test what happens when a connection attempt is made while CONNECTING.
403 Test what happens if we do not wait on the runstate event until
/openbmc/qemu/include/migration/
H A Dregister.h49 * @errp: pointer to Error*, to store an error if it happens.
63 * @errp: pointer to Error*, to store an error if it happens.
237 * @errp: pointer to Error*, to store an error if it happens.
/openbmc/linux/Documentation/process/
H A Dmaintainer-tip.rst50 - interrupt core development happens in the irq/core branch
52 - interrupt chip driver development also happens in the irq/core
59 happens in the timers/core branch, but patches are usually applied in
62 - clocksource/event driver development happens in the timers/core
68 - perf core and architecture support development happens in the
71 - perf tooling development happens in the perf tools maintainer
88 RCU development happens in the linux-rcu tree. The resulting changes
/openbmc/linux/arch/um/os-Linux/
H A Dsignal.c330 * tracing that happens inside the handlers we call for the in unblock_signals()
440 * handle unblocking in the inner call, if it happens, but only in in unblock_signals_hard()
470 * - If it happens before, it can increment it and we'll in unblock_signals_hard()
472 * - If it happens after it'll see 0 for both signals_blocked in unblock_signals_hard()
/openbmc/qemu/docs/devel/migration/
H A Dpostcopy.rst177 background page data (b) but if during a device load a fault happens (5)
205 error happens (in this case, mostly network errors), QEMU cannot easily
207 QEMU instances. On the other hand, when issue happens QEMU on both sides
239 were already migrated to destination VM before the interruption happens.

12345678910>>...88