latency (full) in projects: linux-6.15 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:latency (Results 1 – 25 of 1823) sorted by relevance

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

/linux-6.15/arch/arm/boot/dts/nvidia/
D	tegra30-cpu-opp.dtsi	`9 clock-latency-ns = <100000>; 15 clock-latency-ns = <100000>; 21 clock-latency-ns = <100000>; 27 clock-latency-ns = <100000>; 33 clock-latency-ns = <100000>; 39 clock-latency-ns = <100000>; 45 clock-latency-ns = <100000>; 52 clock-latency-ns = <100000>; 59 clock-latency-ns = <100000>; 66 clock-latency-ns = <100000>; [all …]`
D	tegra20-cpu-opp.dtsi	`9 clock-latency-ns = <400000>; 16 clock-latency-ns = <400000>; 23 clock-latency-ns = <400000>; 29 clock-latency-ns = <400000>; 35 clock-latency-ns = <400000>; 41 clock-latency-ns = <400000>; 48 clock-latency-ns = <400000>; 54 clock-latency-ns = <400000>; 60 clock-latency-ns = <400000>; 66 clock-latency-ns = <400000>; [all …]`
/linux-6.15/arch/sh/lib/
D	memcpy-sh4.S	`31 mov r4,r2 ! 5 MT (0 cycles latency) 33 mov.l @(r0,r5),r7 ! 21 LS (2 cycles latency) 40 3: mov.l @(r0,r5),r1 ! 21 LS (latency=2) ! NMLK 41 mov r7, r3 ! 5 MT (latency=0) ! RQPO 46 mov r1,r6 ! 5 MT (latency=0) 50 mov r1, r7 ! 5 MT (latency=0) 57 3: mov.l @(r0,r5),r1 ! 21 LS (latency=2) ! KLMN 58 mov r7,r3 ! 5 MT (latency=0) ! OPQR 64 mov r1,r6 ! 5 MT (latency=0) 67 mov r1,r7 ! 5 MT (latency=0) [all …]`
/linux-6.15/arch/arm64/boot/dts/qcom/
D	msm8996pro.dtsi	`26 clock-latency-ns = <200000>; 32 clock-latency-ns = <200000>; 38 clock-latency-ns = <200000>; 44 clock-latency-ns = <200000>; 50 clock-latency-ns = <200000>; 56 clock-latency-ns = <200000>; 62 clock-latency-ns = <200000>; 68 clock-latency-ns = <200000>; 74 clock-latency-ns = <200000>; 80 clock-latency-ns = <200000>; [all …]`
/linux-6.15/tools/perf/pmu-events/arch/x86/meteorlake/
D	memory.json	139 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 146 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 152 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 159 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 165 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 172 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 178 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 185 …s when the latency from first dispatch to completion is greater than 2048 cycles. Reported latenc… 191 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 198 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/tigerlake/
D	memory.json	21 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 28 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 33 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 40 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 45 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 52 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 57 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 64 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 69 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 76 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/linux-6.15/Documentation/devicetree/bindings/cpu/
D	idle-states.yaml	44 Idle state parameters (e.g. entry latency) are platform specific and need to 81 \| latency \| 83 \| latency \| 85 \|<------- wakeup-latency ------->\| 93 event conditions. The abort latency is assumed to be negligible 107 entry-latency: Worst case latency required to enter the idle state. The 108 exit-latency may be guaranteed only after entry-latency has passed. 113 wakeup-latency: Maximum delay between the signaling of a wake-up event and the 115 to be entry-latency + exit-latency. 127 wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0) [all …]
/linux-6.15/tools/tracing/latency/
D	Makefile	27 LATENCY-COLLECTOR := $(OUTPUT)latency-collector 28 LATENCY-COLLECTOR_IN := $(LATENCY-COLLECTOR)-in.o 40 all: $(LATENCY-COLLECTOR) 63 $(LATENCY-COLLECTOR): $(LATENCY-COLLECTOR_IN) 64 $(QUIET_LINK)$(CC) $(LDFLAGS) -o $(LATENCY-COLLECTOR) $(LATENCY-COLLECTOR_IN) $(EXTLIBS) 66 latency-collector.%: fixdep FORCE 69 $(LATENCY-COLLECTOR_IN): fixdep FORCE 70 make $(build)=latency-collector 79 $(call QUIET_INSTALL,latency-collector)$(INSTALL) $(LATENCY-COLLECTOR) -m 755 $(DESTDIR)$(BINDIR) 80 @$(STRIP) $(DESTDIR)$(BINDIR)/latency-collector [all …]
/linux-6.15/Documentation/power/
D	pm_qos_interface.rst	10 * CPU latency QoS. 12 per-device latency constraints and PM QoS flags. 14 The latency unit used in the PM QoS framework is the microsecond (usec). 20 A global list of CPU latency QoS requests is maintained along with an aggregated 22 to the request list or elements of the list. For CPU latency QoS, the 32 Will insert an element into the CPU latency QoS list with the target value. 49 Returns the aggregated value for the CPU latency QoS. 53 CPU latency QoS list. 56 Adds a notification callback function to the CPU latency QoS. The callback is 57 called when the aggregated value for the CPU latency QoS is changed. [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/graniterapids/
D	memory.json	68 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 75 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 80 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 87 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 92 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 99 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 104 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 111 …s when the latency from first dispatch to completion is greater than 2048 cycles. Reported latenc… 116 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 123 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/arrowlake/
D	memory.json	159 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 166 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 172 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 179 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 185 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 192 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 198 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 205 …s when the latency from first dispatch to completion is greater than 2048 cycles. Reported latenc… 211 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 218 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/alderlake/
D	memory.json	129 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 136 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 142 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 149 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 155 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 162 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 168 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 175 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 181 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 188 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/lunarlake/
D	memory.json	159 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 166 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 172 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 179 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 185 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 192 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 198 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 205 …s when the latency from first dispatch to completion is greater than 2048 cycles. Reported latenc… 211 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 218 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/emeraldrapids/
D	memory.json	59 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 66 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 71 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 78 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 83 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 90 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 95 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 102 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 107 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 114 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	memory.json	59 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 66 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 71 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 78 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 83 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 90 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 95 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 102 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 107 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 114 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… [all …]
/linux-6.15/kernel/
D	latencytop.c	3 * latencytop.c: Latency display infrastructure 10 * CONFIG_LATENCYTOP enables a kernel latency tracking infrastructure that is 11 * used by the "latencytop" userspace tool. The latency that is tracked is not 12 * the 'traditional' interrupt latency (which is primarily caused by something 13 * else consuming CPU), but instead, it is the latency an application encounters 17 * 1) System level latency 18 * 2) Per process latency 20 * The latency is stored in fixed sized data structures in an accumulated form; 21 * if the "same" latency cause is hit twice, this will be tracked as one entry 22 * in the data structure. Both the count, total accumulated latency and maximum [all …]
/linux-6.15/arch/arm64/boot/dts/rockchip/
D	rk3588-opp.dtsi	`11 clock-latency-ns = <40000>; 16 clock-latency-ns = <40000>; 21 clock-latency-ns = <40000>; 27 clock-latency-ns = <40000>; 32 clock-latency-ns = <40000>; 43 clock-latency-ns = <40000>; 48 clock-latency-ns = <40000>; 53 clock-latency-ns = <40000>; 58 clock-latency-ns = <40000>; 63 clock-latency-ns = <40000>; [all …]`
/linux-6.15/tools/perf/Documentation/
D	cpu-and-latency-overheads.txt	1 CPU and latency overheads 9 'latency' columns for CPU and wall-clock time correspondingly). 12 latency overhead is useful to improve 'latency'. It's important to understand 16 latency of a single interactive program build. 21 While the latency overhead is: 'foo' - 90%, 'bar' - 10%. If we try to optimize 26 By default, perf shows only CPU overhead. To show latency overhead, use 27 'perf record --latency' and 'perf report': 30 Overhead Latency Command 38 To sort by latency overhead, use 'perf report --latency': 41 Latency Overhead Command [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/ivybridge/
D	memory.json	11 "BriefDescription": "Loads with latency value being above 128", 18 "PublicDescription": "Loads with latency value being above 128.", 23 "BriefDescription": "Loads with latency value being above 16", 30 "PublicDescription": "Loads with latency value being above 16.", 35 "BriefDescription": "Loads with latency value being above 256", 42 "PublicDescription": "Loads with latency value being above 256.", 47 "BriefDescription": "Loads with latency value being above 32", 54 "PublicDescription": "Loads with latency value being above 32.", 59 "BriefDescription": "Loads with latency value being above 4", 66 "PublicDescription": "Loads with latency value being above 4.", [all …]
/linux-6.15/tools/tracing/rtla/src/
D	timerlat.bpf.c	84 unsigned long long latency, in update_summary() argument 91 map_set(map, SUMMARY_CURRENT, latency); in update_summary() 97 if (latency > map_get(map, SUMMARY_MAX)) in update_summary() 98 map_set(map, SUMMARY_MAX, latency); in update_summary() 100 if (latency < map_get(map, SUMMARY_MIN) \|\| map_get(map, SUMMARY_COUNT) == 0) in update_summary() 101 map_set(map, SUMMARY_MIN, latency); in update_summary() 104 map_set(map, SUMMARY_SUM, map_get(map, SUMMARY_SUM) + latency); in update_summary() 121 unsigned long long latency, latency_us; in handle_timerlat_sample() local 127 latency = tp_args->timer_latency / output_divisor; in handle_timerlat_sample() 129 bucket = latency / bucket_size; in handle_timerlat_sample() [all …]
/linux-6.15/drivers/char/tpm/st33zp24/
D	spi.c	41 * Between command and response, there are latency byte (up to 15 47 * some latency byte before the answer is available (max 15). 60 int latency; member 119 memset(&phy->tx_buf[total_length], TPM_DUMMY_BYTE, phy->latency); in st33zp24_spi_send() 121 spi_xfer.len = total_length + phy->latency; in st33zp24_spi_send() 125 ret = phy->rx_buf[total_length + phy->latency - 1]; in st33zp24_spi_send() 155 phy->latency + tpm_size); in st33zp24_spi_read8_reg() 157 spi_xfer.len = total_length + phy->latency + tpm_size; in st33zp24_spi_read8_reg() 162 ret = phy->rx_buf[total_length + phy->latency - 1]; in st33zp24_spi_read8_reg() 164 memcpy(tpm_data, phy->rx_buf + total_length + phy->latency, in st33zp24_spi_read8_reg() [all …]
/linux-6.15/arch/arm/boot/dts/samsung/
D	exynos4212.dtsi	`65 clock-latency-ns = <200000>; 70 clock-latency-ns = <200000>; 75 clock-latency-ns = <200000>; 80 clock-latency-ns = <200000>; 85 clock-latency-ns = <200000>; 90 clock-latency-ns = <200000>; 95 clock-latency-ns = <200000>; 101 clock-latency-ns = <200000>; 106 clock-latency-ns = <200000>; 111 clock-latency-ns = <200000>; [all …]`
/linux-6.15/tools/perf/pmu-events/arch/x86/icelake/
D	memory.json	84 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 91 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 96 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 103 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 108 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 115 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 120 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 127 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 132 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 139 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/linux-6.15/tools/perf/pmu-events/arch/x86/rocketlake/
D	memory.json	84 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 91 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 96 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 103 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 108 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 115 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 120 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 127 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 132 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 139 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/linux-6.15/Documentation/devicetree/bindings/power/
D	domain-idle-state.yaml	`31 entry-latency-us: 33 The worst case latency in microseconds required to enter the idle 34 state. Note that, the exit-latency-us duration may be guaranteed only 35 after the entry-latency-us has passed. 37 exit-latency-us: 39 The worst case latency in microseconds required to exit the idle 64 - entry-latency-us 65 - exit-latency-us 76 entry-latency-us = <20>; 77 exit-latency-us = <40>;`

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