latency (full) in projects: kernel - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/graniterapids/
D	memory.json	3 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 10 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 15 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 22 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 27 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 34 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 39 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 46 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 51 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 58 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
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>; 51 clock-latency-ns = <100000>; 57 clock-latency-ns = <100000>; 63 clock-latency-ns = <100000>; [all …]`
D	tegra20-cpu-opp.dtsi	`9 clock-latency-ns = <400000>; 15 clock-latency-ns = <400000>; 21 clock-latency-ns = <400000>; 27 clock-latency-ns = <400000>; 33 clock-latency-ns = <400000>; 39 clock-latency-ns = <400000>; 46 clock-latency-ns = <400000>; 52 clock-latency-ns = <400000>; 58 clock-latency-ns = <400000>; 64 clock-latency-ns = <400000>; [all …]`
/kernel/linux/linux-6.6/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 …]`
/kernel/linux/linux-6.6/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 …]`
/kernel/linux/linux-5.10/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 …]`
/kernel/linux/linux-6.6/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 …]`
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/tigerlake/
D	memory.json	19 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 26 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 31 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 38 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 43 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 50 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 55 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 62 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 67 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 74 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/meteorlake/
D	memory.json	124 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 131 …s when the latency from first dispatch to completion is greater than 1024 cycles. Reported latenc… 137 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 144 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 150 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 157 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 163 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 170 …s when the latency from first dispatch to completion is greater than 2048 cycles. Reported latenc… 176 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 183 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… [all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/opp/
D	qcom-nvmem-cpufreq.txt	`152 clock-latency-ns = <200000>; 158 clock-latency-ns = <200000>; 164 clock-latency-ns = <200000>; 170 clock-latency-ns = <200000>; 176 clock-latency-ns = <200000>; 182 clock-latency-ns = <200000>; 188 clock-latency-ns = <200000>; 194 clock-latency-ns = <200000>; 200 clock-latency-ns = <200000>; 206 clock-latency-ns = <200000>; [all …]`
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
D	idle-states.yaml	39 Idle state parameters (e.g. entry latency) are platform specific and need to 61 \| latency \| 63 \| latency \| 65 \|<------- wakeup-latency ------->\| 73 event conditions. The abort latency is assumed to be negligible 87 entry-latency: Worst case latency required to enter the idle state. The 88 exit-latency may be guaranteed only after entry-latency has passed. 93 wakeup-latency: Maximum delay between the signaling of a wake-up event and the 95 to be entry-latency + exit-latency. 107 wakeup-delay = exit-latency + max(entry-latency - (now - entry-timestamp), 0) [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlake/
D	memory.json	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 128 cycles. Reported latency… 129 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 136 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 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 256 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 32 cycles. Reported latency… 168 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 175 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/sapphirerapids/
D	memory.json	53 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 60 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 65 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 72 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 77 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 84 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 89 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 96 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 101 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 108 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelake/
D	memory.json	75 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 82 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 87 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 94 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 99 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 106 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 111 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 118 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 123 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 130 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/rocketlake/
D	memory.json	75 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 82 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 87 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 94 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 99 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 106 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 111 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 118 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 123 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 130 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/ivybridge/
D	memory.json	10 "BriefDescription": "Loads with latency value being above 128", 16 "PublicDescription": "Loads with latency value being above 128.", 21 "BriefDescription": "Loads with latency value being above 16", 27 "PublicDescription": "Loads with latency value being above 16.", 32 "BriefDescription": "Loads with latency value being above 256", 38 "PublicDescription": "Loads with latency value being above 256.", 43 "BriefDescription": "Loads with latency value being above 32", 49 "PublicDescription": "Loads with latency value being above 32.", 54 "BriefDescription": "Loads with latency value being above 4", 60 "PublicDescription": "Loads with latency value being above 4.", [all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
D	domain-idle-state.yaml	`30 entry-latency-us: 32 The worst case latency in microseconds required to enter the idle 33 state. Note that, the exit-latency-us duration may be guaranteed only 34 after the entry-latency-us has passed. 36 exit-latency-us: 38 The worst case latency in microseconds required to exit the idle 49 - entry-latency-us 50 - exit-latency-us 61 entry-latency-us = <20>; 62 exit-latency-us = <40>;`
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/icelakex/
D	memory.json	19 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 26 …s when the latency from first dispatch to completion is greater than 128 cycles. Reported latency… 31 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 38 …ds when the latency from first dispatch to completion is greater than 16 cycles. Reported latency… 43 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 50 …s when the latency from first dispatch to completion is greater than 256 cycles. Reported latency… 55 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 62 …ds when the latency from first dispatch to completion is greater than 32 cycles. Reported latency… 67 …"BriefDescription": "Counts randomly selected loads when the latency from first dispatch to comple… 74 …ds when the latency from first dispatch to completion is greater than 4 cycles. Reported latency … [all …]
/kernel/linux/linux-6.6/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 …]

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