After (full) in projects: linux-6.14.4 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...279

/linux-6.14.4/tools/perf/pmu-events/
D	metric_test.py	`44 after = before 45 self.assertEqual(ParsePerfJson(before).ToPerfJson(), after) 50 after = before 51 self.assertEqual(ParsePerfJson(before).ToPerfJson(), after) 56 after = before 57 self.assertEqual(ParsePerfJson(before).ToPerfJson(), after) 61 after = before 62 self.assertEqual(ParsePerfJson(before).ToPerfJson(), after) 67 after = f'({before})' 68 self.assertEqual(ParsePerfJson(before).ToPerfJson(), after) [all …]`
/linux-6.14.4/Documentation/hwmon/
D	isl68137.rst	25 Publicly available (after August 2020 launch) at the Renesas website 35 Publicly available (after August 2020 launch) at the Renesas website 45 Publicly available (after August 2020 launch) at the Renesas website 55 Publicly available (after August 2020 launch) at the Renesas website 65 Publicly available (after August 2020 launch) at the Renesas website 75 Publicly available (after August 2020 launch) at the Renesas website 85 Publicly available (after August 2020 launch) at the Renesas website 95 Publicly available (after August 2020 launch) at the Renesas website 105 Publicly available (after August 2020 launch) at the Renesas website 115 Publicly available (after August 2020 launch) at the Renesas website [all …]
/linux-6.14.4/tools/testing/selftests/drivers/net/netdevsim/
D	hw_stats_l3.sh	215 check_err $? "$type stats reported as not used after both device and netdevsim request" 217 check_err $? "$type stats reported as not requested after device request" 221 check_err $? "$type stats reported as used after netdevsim request withdrawn" 225 check_err $? "$type stats reported as not used after netdevsim request reenabled" 229 check_err $? "$type stats reported as used after device request withdrawn" 231 check_err $? "$type stats reported as requested after device request withdrawn" 235 check_err $? "$type stats reported as used after both requests withdrawn" 265 check_err $? "$type stats reported as used after bounce" 267 check_err $? "$type stats reported as requested after bounce" 272 check_err $? "$type stats reported as not used after both device and netdevsim request" [all …]
D	nexthop.sh	126 check_err $? "Wrong nexthop occupancy after delete" 167 check_err $? "Wrong nexthop occupancy after delete" 178 check_err $? "Wrong nexthop occupancy after delete" 227 check_err $? "Wrong nexthop occupancy after delete" 243 check_err $? "Wrong nexthop occupancy after delete" 307 check_err $? "Unexpected nexthop group entry after failure" 310 check_err $? "Wrong nexthop occupancy after failure" 361 check_err $? "Unexpected nexthop group entry after failure" 369 check_err $? "Wrong nexthop occupancy after failure" 420 log_test "Bucket migration after idle timer" [all …]
/linux-6.14.4/drivers/greybus/
D	greybus_trace.h	60 * 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-6.14.4/drivers/net/wireguard/
D	timers.c	13 * - Timer for retransmitting the handshake if we don't hear back after 16 * - Timer for sending empty packet if we have received a packet but after have 19 * - Timer for initiating new handshake if we have sent a packet but after have 23 * - Timer for zeroing out all ephemeral keys after `(REJECT_AFTER_TIME * 3)` ms 47 pr_debug("%s: Handshake for peer %llu (%pISpfsc) did not complete after %d attempts, giving up\n", in wg_expired_retransmit_handshake() 65 …pr_debug("%s: Handshake for peer %llu (%pISpfsc) did not complete after %d seconds, retrying (try … in wg_expired_retransmit_handshake() 95 …pr_debug("%s: Retrying handshake with peer %llu (%pISpfsc) because we stopped hearing back after %… in wg_expired_new_handshake() 144 /* Should be called after an authenticated data packet is sent. / 153 / Should be called after an authenticated data packet is received. / 165 / Should be called after any type of authenticated packet is sent, whether [all …]
/linux-6.14.4/tools/testing/selftests/net/forwarding/
D	bridge_locked_port.sh	105 check_fail $? "Ping worked after locking port, but before adding FDB entry" 110 check_err $? "Ping did not work after locking port and adding FDB entry" 116 check_err $? "Ping did not work after unlocking port and removing FDB entry." 135 check_fail $? "Ping through vlan worked after locking port, but before adding FDB entry" 140 check_err $? "Ping through vlan did not work after locking port and adding FDB entry" 146 check_err $? "Ping through vlan did not work after unlocking port and removing FDB entry" 164 check_fail $? "Ping6 worked after locking port, but before adding FDB entry" 168 check_err $? "Ping6 did not work after locking port and adding FDB entry" 174 check_err $? "Ping6 did not work after unlocking port and removing FDB entry" 206 check_err $? "Ping did not work after replacing FDB entry" [all …]
/linux-6.14.4/scripts/
D	config	`29 --enable-after\|-E beforeopt option 30 Enable option directly after other option 31 --disable-after\|-D beforeopt option 32 Disable option directly after other option 33 --module-after\|-M beforeopt option 34 Turn option into module directly after other option 85 local after="$2" 89 sed -e "s$SED_DELIM$before$SED_DELIM$after$SED_DELIM" "$infile" >"$tmpfile" 152 --*-after\|-E\|-D\|-M) 208 --enable-after\|-E) [all …]`
/linux-6.14.4/tools/testing/selftests/drivers/net/mlxsw/
D	fib_offload.sh	87 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-6.14.4/tools/testing/selftests/media_tests/
D	regression_test.txt	`2 and unregister paths. There have a few problems that result in use-after 18 Regressions test for cdev use-after-free error on /dev/mediaX when driver 22 and cdev use-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 use-after-free errors or mutex lock errors.`
/linux-6.14.4/tools/testing/selftests/arm64/pauth/
D	pac.c	335 struct signatures after; in TEST() local 345 sign_specific(&after, ARBITRARY_VALUE); in TEST() 347 ASSERT_EQ(before.keyia, after.keyia) TH_LOG("keyia changed after context switching"); in TEST() 348 ASSERT_EQ(before.keyib, after.keyib) TH_LOG("keyib changed after context switching"); in TEST() 349 ASSERT_EQ(before.keyda, after.keyda) TH_LOG("keyda changed after context switching"); in TEST() 350 ASSERT_EQ(before.keydb, after.keydb) TH_LOG("keydb changed after context switching"); in TEST() 358 size_t after; in TEST() local 368 after = keyg_sign(ARBITRARY_VALUE); in TEST() 370 ASSERT_EQ(before, after) TH_LOG("keyg changed after context switching"); in TEST()
/linux-6.14.4/tools/perf/pmu-events/arch/x86/icelake/
D	frontend.json	101 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 108 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 113 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 120 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 125 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 132 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 137 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 144 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 149 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 156 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/rocketlake/
D	frontend.json	101 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 108 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 113 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 120 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 125 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 132 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 137 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 144 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 149 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 156 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/icelakex/
D	frontend.json	101 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 108 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 113 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 120 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 125 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 132 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 137 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 144 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 149 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 156 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/tigerlake/
D	frontend.json	101 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 108 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 113 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 120 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 125 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 132 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 137 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 144 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 149 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 156 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/include/trace/events/
D	ksm.h	39 * ksm_start_scan - called after a new ksm scan is started 54 * ksm_stop_scan - called after a new ksm scan has completed 69 * ksm_enter - called after a new process has been added / removed from ksm 93 * ksm_enter - called after a new process has been added to ksm 107 * ksm_exit - called after a new process has been removed from ksm 121 * ksm_merge_one_page - called after a page has been merged 155 * ksm_merge_with_ksm_page - called after a page has been merged with a ksm page 193 * ksm_remove_ksm_page - called after a ksm page has been removed 217 * ksm_remove_rmap_item - called after a rmap_item has been removed from the 249 * ksm_advisor - called after the advisor has run
/linux-6.14.4/drivers/platform/mellanox/
D	mlxbf-bootctl.h	10 * Request that the on-chip watchdog be enabled, or disabled, after 14 * will not be enabled after the next soft reset. Non-zero errors are 21 * after the next chip soft reset. Returns the interval as set by 46 * after the next soft reset. For a specified valid boot mode, the 48 * MLXBF_BOOTCTL_SET_RESET_ACTION after the next chip soft reset; in 49 * particular, after that reset, the action for the now next reset can 53 * MLXBF_BOOTCTL_SET_RESET_ACTION be taken after the next chip soft reset. 61 * reset after the next soft reset; this will be one of the valid
/linux-6.14.4/include/linux/
D	suspend.h	65 * @prepare() is called right after devices have been suspended (ie. the 74 * @prepare_late is called before disabling nonboot CPUs and after 86 * @wake: Called when the system has just left a sleep state, right after 91 * after @prepare_late and @enter(), even if one of them fails. 97 * that implement @prepare(). If implemented, it is always called after 98 * @enter() and @wake(), even if any of them fails. It is executed after 108 * @end: Called by the PM core right after resuming devices, to indicate to 269 * arch_suspend_enable_irqs - enable IRQs after suspend 320 * Called right after shrinking memory and before freezing devices. 322 * @end: Called by the PM core right after resuming devices, to indicate to [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/graniterapids/
D	frontend.json	110 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 117 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 122 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 129 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 134 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 141 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 146 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 153 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 158 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 165 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/emeraldrapids/
D	frontend.json	98 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 105 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 110 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 117 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 122 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 129 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 134 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 141 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 146 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 153 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	frontend.json	98 "BriefDescription": "Retired instructions after front-end starvation of at least 1 cycle", 105 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 110 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 117 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… 122 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 129 …"PublicDescription": "Counts retired instructions that are delivered to the back-end after a front… 134 "BriefDescription": "Retired instructions after front-end starvation of at least 2 cycles", 141 …"PublicDescription": "Retired instructions that are fetched after an interval where the front-end … 146 …"BriefDescription": "Retired instructions that are fetched after an interval where the front-end d… 153 …"PublicDescription": "Counts retired instructions that are fetched after an interval where the fro… [all …]
/linux-6.14.4/Documentation/driver-api/md/
D	raid5-cache.rst	34 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-6.14.4/drivers/scsi/mvsas/
D	mv_64xx.h	`53 /* 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-6.14.4/Documentation/devicetree/bindings/power/reset/
D	gpio-restart.yaml	23 reset. After a delay specified by active-delay, the GPIO is set to inactive, thus causing an 24 active->inactive edge, triggering negative edge triggered reset. After a delay specified by 25 inactive-delay, the GPIO is driven active again. After a delay specified by wait-delay, the 51 description: Delay (default 100) to wait after driving gpio active [ms] 56 description: Delay (default 100) to wait after driving gpio inactive [ms] 61 description: Delay (default 3000) to wait after completing restart sequence [ms]
/linux-6.14.4/Documentation/power/
D	suspend-and-interrupts.rst	13 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()).

12 3 4 5 6 7 8 9 10 >>...279