Home
last modified time | relevance | path

Searched full:after (Results 1 – 25 of 6128) sorted by relevance

12345678910>>...246

/Linux-v5.4/drivers/greybus/
Dgreybus_trace.h60 * Occurs after an incoming request message has been received
65 * Occurs after an incoming response message has been received,
66 * after its matching request has been found.
71 * Occurs after an operation has been canceled, possibly before the
78 * been queued for sending, this occurs after it is sent.
127 * Occurs after a new operation is created for an outgoing request
133 * Occurs after a new core operation has been created.
138 * Occurs after a new operation has been created for an incoming
150 * Occurs when an operation has been marked active, after updating
199 * Occurs after a new connection is successfully created.
[all …]
/Linux-v5.4/scripts/
Dconfig26 --enable-after|-E beforeopt option
27 Enable option directly after other option
28 --disable-after|-D beforeopt option
29 Disable option directly after other option
30 --module-after|-M beforeopt option
31 Turn option into module directly after other option
82 local after="$2"
86 sed -e "s:$before:$after:" "$infile" >"$tmpfile"
149 --*-after|-E|-D|-M)
205 --enable-after|-E)
[all …]
/Linux-v5.4/tools/testing/selftests/pidfd/
Dpidfd_wait.c94 "%s test: unexpected status received after waiting on process with pid %d and pidfd %d: %s\n", in test_pidfd_wait_simple()
100 …"%s test: unexpected si_signo value %d received after waiting on process with pid %d and pidfd %d:… in test_pidfd_wait_simple()
106 …"%s test: unexpected si_code value %d received after waiting on process with pid %d and pidfd %d: … in test_pidfd_wait_simple()
112 …"%s test: unexpected si_pid value %d received after waiting on process with pid %d and pidfd %d: %… in test_pidfd_wait_simple()
156 …"%s test: unexpected si_signo value %d received after waiting on process with pid %d and pidfd %d:… in test_pidfd_wait_states()
162 …"%s test: unexpected si_code value %d received after waiting on process with pid %d and pidfd %d: … in test_pidfd_wait_states()
168 …"%s test: unexpected si_pid value %d received after waiting on process with pid %d and pidfd %d: %… in test_pidfd_wait_states()
186 …"%s test: unexpected si_signo value %d received after waiting on process with pid %d and pidfd %d:… in test_pidfd_wait_states()
192 …"%s test: unexpected si_code value %d received after waiting on process with pid %d and pidfd %d: … in test_pidfd_wait_states()
198 …"%s test: unexpected si_pid value %d received after waiting on process with pid %d and pidfd %d: %… in test_pidfd_wait_states()
[all …]
/Linux-v5.4/tools/testing/selftests/media_tests/
Dregression_test.txt2 and unregister paths. There have a few problems that result in user-after
18 Regressions test for cdev user-after free error on /dev/mediaX when driver
22 and cdev user-after-free fixes. This opens media dev files and sits in
35 device file goes away after unbind, device file name changes. Start the
37 after unbind, /dev/media1 or /dev/media2 could get created. The idea is
43 Run dmesg looking for any user-after free errors or mutex lock errors.
/Linux-v5.4/tools/testing/selftests/drivers/net/mlxsw/
Dfib_offload.sh87 check_err $? "lowest metric not offloaded after append"
95 check_err $? "lowest metric not offloaded after prepend"
136 check_err $? "multipath route not offloaded after delete & add"
143 check_err $? "lowest metric not offloaded after append"
152 check_err $? "lowest metric not offloaded after prepend"
179 check_err $? "prefix route not offloaded after replace"
186 check_err $? "multipath route not offloaded after replace"
192 check_err $? "prefix route offloaded after 'replacing' multipath route"
194 check_err $? "multipath route not offloaded after being 'replaced' by prefix route"
201 check_err $? "multipath route not offloaded after replacing multipath route"
[all …]
/Linux-v5.4/include/linux/usb/
Dtypec_dp.h28 TYPEC_DP_STATE_A = TYPEC_STATE_MODAL, /* Not supported after v1.0b */
29 TYPEC_DP_STATE_B, /* Not supported after v1.0b */
33 TYPEC_DP_STATE_F, /* Not supported after v1.0b */
53 DP_PIN_ASSIGN_A, /* Not supported after v1.0b */
54 DP_PIN_ASSIGN_B, /* Not supported after v1.0b */
58 DP_PIN_ASSIGN_F, /* Not supported after v1.0b */
71 #define DP_CAP_GEN2 BIT(3) /* Reserved after v1.0b */
96 #define DP_CONF_SIGNALING_GEN_2 BIT(3) /* Reserved after v1.0b */
/Linux-v5.4/tools/testing/selftests/vm/
Dthuge-gen.c145 unsigned long before, after; in test_mmap() local
154 after = read_free(size); in test_mmap()
155 Dprintf("before %lu after %lu diff %ld size %lu\n", in test_mmap()
156 before, after, before - after, size); in test_mmap()
157 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_mmap()
166 unsigned long before, after; in test_shmget() local
185 after = read_free(size); in test_shmget()
187 Dprintf("before %lu after %lu diff %ld size %lu\n", in test_shmget()
188 before, after, before - after, size); in test_shmget()
189 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_shmget()
/Linux-v5.4/Documentation/devicetree/bindings/power/reset/
Dgpio-restart.txt14 reset. After a delay specified by active-delay, the GPIO is set to
16 triggered reset. After a delay specified by inactive-delay, the GPIO
17 is driven active again. After a delay specified by wait-delay, the
40 - active-delay: Delay (default 100) to wait after driving gpio active [ms]
41 - inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
42 - wait-delay: Delay (default 3000) to wait after completing restart
Dgpio-poweroff.txt12 triggering positive edge triggered power off. After a delay of 100ms,
14 triggering negative edge triggered power off. After another 100ms
16 the CPU still running after a 3000ms delay, a WARN_ON(1) is emitted.
30 - active-delay-ms: Delay (default 100) to wait after driving gpio active
31 - inactive-delay-ms: Delay (default 100) to wait after driving gpio inactive
/Linux-v5.4/tools/nfsd/
Dinject_fault.sh44 AFTER=`mktemp`
47 dmesg > $AFTER
48 # Capture lines that only exist in the $AFTER file
49 diff $BEFORE $AFTER | grep ">"
50 rm -f $BEFORE $AFTER
/Linux-v5.4/include/linux/
Dsuspend.h121 * @prepare() is called right after devices have been suspended (ie. the
130 * @prepare_late is called before disabling nonboot CPUs and after
142 * @wake: Called when the system has just left a sleep state, right after
147 * after @prepare_late and @enter(), even if one of them fails.
153 * that implement @prepare(). If implemented, it is always called after
154 * @enter() and @wake(), even if any of them fails. It is executed after
164 * @end: Called by the PM core right after resuming devices, to indicate to
323 * arch_suspend_enable_irqs - enable IRQs after suspend
373 * Called right after shrinking memory and before freezing devices.
375 * @end: Called by the PM core right after resuming devices, to indicate to
[all …]
Dwait.h296 * wake_up() has to be called after changing any variable that could
335 * wake_up() has to be called after changing any variable that could
362 * wake_up() has to be called after changing any variable that could
366 * 0 if the @condition evaluated to %false after the @timeout elapsed,
367 * 1 if the @condition evaluated to %true after the @timeout elapsed,
420 * @cmd2: the command will be executed after sleep
426 * wake_up() has to be called after changing any variable that could
449 * wake_up() has to be called after changing any variable that could
479 * wake_up() has to be called after changing any variable that could
483 * 0 if the @condition evaluated to %false after the @timeout elapsed,
[all …]
Dpm.h58 * the device from being registered after it has returned (the driver's
63 * that the PM core can execute it once again (e.g. after a new child has
75 * executed directly after @prepare() and it must ensure the proper
76 * functioning of the device after the system resume.
95 * The PM core executes subsystem-level @complete() after it has executed
102 * proper functioning of the device after the system resume. To this end,
110 * type), but generally the device must be quiescent after subsystem-level
112 * Subsystem-level @suspend() is executed for all devices after invoking
119 * @resume: Executed after waking the system up from a sleep state in which the
128 * Subsystem-level @resume() is executed for all devices after invoking
[all …]
/Linux-v5.4/Documentation/driver-api/md/
Draid5-cache.rst34 The write-through cache will cache all data on cache disk first. After the data
36 two-step write will guarantee MD can recover correct data after unclean
40 filesystems) after the data is safe on RAID disks, so cache disk failure
57 RAID disks only after the data becomes a full stripe write. This will
62 filesystems) right after the data hits cache disk. The data is flushed to raid
63 disks later after specific conditions met. So cache disk failure will cause
92 parity to the log, writes the data and parity to RAID disks after the data and
99 MD will calculate parity for the data and write parity into the log. After this
105 After an unclean shutdown, MD does recovery. MD reads all meta data and data
/Linux-v5.4/drivers/scsi/mvsas/
Dmv_64xx.h53 /* ports 1-3 follow after this */
56 /* ports 5-7 follow after this */
60 /* ports 1-3 follow after this */
62 /* ports 5-7 follow after this */
68 /* ports 1-3 follow after this */
71 /* ports 5-7 follow after this */
75 /* ports 1-3 follow after this */
78 /* ports 5-7 follow after this */
/Linux-v5.4/tools/perf/pmu-events/arch/x86/icelake/
Dfrontend.json277 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro…
286 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
292 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro…
301 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
307 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
316 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
322 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
331 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
337 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front…
346 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
[all …]
/Linux-v5.4/Documentation/power/
Dsuspend-and-interrupts.rst13 suspend after the "late" phase of suspending devices (that is, after all of the
17 The rationale for doing so is that after the "late" phase of device suspend
22 not prepared for interrupts triggering after their devices had been suspended.
52 for it will be executed as usual after suspend_device_irqs(), even if the
72 After wakeup, it generally is better to disable that input to prevent the
90 already suspended. However, after suspend_device_irqs() interrupt handlers are
101 interrupts right after the "noirq" phase of suspending devices.
122 interrupts (interrupt handlers are invoked after suspend_device_irqs()) are
124 handlers are not invoked after suspend_device_irqs()).
/Linux-v5.4/Documentation/core-api/
Dcachetlb.rst10 after the interface is invoked.
34 The most severe flush of all. After this interface runs,
44 the TLB. After running, this interface must make sure that
46 'mm' will be visible to the cpu. That is, after running,
57 address translations from the TLB. After running, this
60 'start' to 'end-1' will be visible to the cpu. That is, after
83 After running, this interface must make sure that any previous
86 is, after running, there will be no entries in the TLB for
140 the caches. That is, after running, there will be no cache
149 the caches. That is, after running, there will be no cache
[all …]
/Linux-v5.4/Documentation/m68k/
Dbuddha-driver.rst33 as long as $48 is not touched. After $48 has been written,
146 value 0 (Default after reset)
147 497ns Select (7 clock cycles) , IOR/IOW after 172ns (2 clock cycles)
152 639ns Select (9 clock cycles), IOR/IOW after 243ns (3 clock cycles)
155 781ns Select (11 clock cycles), IOR/IOW after 314ns (4 clock cycles)
158 355ns Select (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
161 355ns Select (5 clock cycles), IOR/IOW after 172ns (2 clock cycles)
164 355ns Select (5 clock cycles), IOR/IOW after 243ns (3 clock cycles)
167 1065ns Select (15 clock cycles), IOR/IOW after 314ns (4 clock cycles)
170 355ns Select, (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
[all …]
/Linux-v5.4/kernel/rcu/
Dsync.c31 * Must be called after rcu_sync_init() and before first use.
55 * rcu_sync_exit(), so that it is invoked after a grace period following the
67 * readers back onto their fastpaths (after a grace period). If both
84 * We're at least a GP after the GP_IDLE->GP_ENTER transition. in rcu_sync_func()
97 * We're at least a GP after the last rcu_sync_exit(); eveybody in rcu_sync_func()
111 * a slowpath during the update. After this function returns, all
159 * rcu_sync_exit() - Allow readers back onto fast path after grace period
163 * now allow readers to make use of their fastpaths after a grace period
164 * has elapsed. After this grace period has completed, all subsequent
/Linux-v5.4/Documentation/media/kapi/
Ddtv-frontend.rst107 in order to remove the tuner from the I2C bus after a channel is
115 removed in the future, after we have all existing drivers supporting
237 measurement usually comes from the tuner (e. g. after ``FE_HAS_CARRIER``,
241 as the frontend measures it indirectly from other parameters (e. g. after
244 Having it available after inner FEC is more common.
247 - Those counters measure the number of bits and bit errors errors after
249 (after Viterbi, LDPC or other inner code).
252 (e. g. after ``FE_HAS_SYNC`` or after ``FE_HAS_LOCK``,
263 after ``FE_HAS_VITERBI``, see :c:type:`fe_status`).
266 - Those counters measure the number of blocks and block errors errors after
[all …]
/Linux-v5.4/tools/testing/selftests/powerpc/pmu/ebb/
Dpmae_handling_test.c29 static uint64_t before, after; variable
49 after = mfspr(SPRN_MMCR0); in syscall_ebb_callee()
50 if (before != after) in syscall_ebb_callee()
90 printf("Saw MMCR0 before 0x%lx after 0x%lx\n", before, after); in test_body()
/Linux-v5.4/mm/
DKconfig.debug17 Unmap pages from the kernel linear mapping after free_pages().
24 use-after-free). The error reports for these checks can be augmented
29 fill the pages with poison patterns after free_pages() and verify
32 incorrect warnings of memory corruption after a resume because free
66 bool "Poison pages after freeing"
69 Fill the pages with poison patterns after free_pages() and verify
/Linux-v5.4/include/drm/
Ddrm_bridge.h156 * This callback should disable the bridge. It is called right after the
158 * element is a bridge this means it's called after that bridge's
160 * it's called right after the encoder's
176 * after the @mode_set callback for the preceding element in the display
224 * This callback should enable the bridge. It is called right after
226 * preceding element is a bridge this means it's called after that
228 * &drm_encoder it's called right after the encoder's
269 * This callback should enable the bridge. It is called right after
271 * preceding element is a bridge this means it's called after that
273 * is a &drm_encoder it's called right after the encoder's
[all …]
/Linux-v5.4/tools/perf/pmu-events/arch/x86/cascadelakex/
Dfrontend.json250 …Decode Queue (IDQ) is full. SBD-to-MITE switch true penalty cycles happen after the merge mux (MM)…
257 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
270 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end h…
283 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
364 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end h…
377 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end h…
383 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after the fro…
391 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
404 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
417 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d…
[all …]

12345678910>>...246