Searched full:therefore (Results 1 – 25 of 2751) sorted by relevance
12345678910>>...111
/linux-6.12.1/tools/perf/pmu-events/arch/x86/jaketown/ |
D | uncore-interconnect.json | 532 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 542 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 552 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 562 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 572 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 582 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 592 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 602 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 612 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… 622 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI 'speed' (for e… [all …]
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/ivytown/ |
D | uncore-interconnect.json | 236 … re-acquire it later when they get to the head of the queue. This will therefore track the number… 993 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1003 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1013 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1023 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1033 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1043 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1053 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1063 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1073 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… [all …]
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/haswellx/ |
D | uncore-interconnect.json | 7 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 17 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 973 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 983 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 993 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1003 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1013 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1023 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1033 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1043 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… [all …]
|
/linux-6.12.1/tools/perf/pmu-events/arch/x86/broadwellx/ |
D | uncore-interconnect.json | 7 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 17 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 972 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 982 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 992 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1002 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1012 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1022 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1032 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… 1042 …therefore it takes twice as many fits to transmit a flit. When one talks about QPI speed (for exa… [all …]
|
/linux-6.12.1/Documentation/networking/device_drivers/hamradio/ |
D | baycom.rst | 22 therefore it supports just about every bit bang modem on a 65 and can therefore be fed from the parallel port and does not require 89 but they are now true kernel network interfaces. Installation is therefore 143 a reasonable DCD algorithm in software. Therefore, if your radio 159 startup time. Therefore the baycom drivers subsequently won't be able to 160 access a serial port. You might therefore find it necessary to release
|
/linux-6.12.1/Documentation/networking/ |
D | x25.rst | 15 I therefore decided to write the implementation such that as far as the 17 layer of the Linux kernel and therefore it did not concern itself with 18 implementation of LAPB. Therefore the LAPB modules would be called by
|
D | gtp.rst | 165 There is only one GTP-U entity (and therefore SGSN/GGSN/S-GW/PDN-GW 173 Therefore: 189 Therefore no two remote GTP-U endpoints shall send traffic to a 199 Therefore, the receiving side identifies tunnels exclusively based on 242 Therefore for a given UE the mapping in IP to PDN network is:
|
/linux-6.12.1/drivers/pci/controller/dwc/ |
D | Kconfig | 38 and therefore the driver re-uses the DesignWare core functions to 85 on DesignWare hardware and therefore the driver re-uses the 97 on DesignWare hardware and therefore the driver re-uses the 200 DesignWare hardware and therefore the driver re-uses the 352 hardware and therefore the driver re-uses the DesignWare core 438 DesignWare hardware and therefore the driver re-uses the 450 on DesignWare hardware and therefore the driver re-uses the
|
/linux-6.12.1/tools/memory-model/Documentation/ |
D | control-dependencies.txt | 5 do not support them. One purpose of this document is therefore to 12 Therefore, a load-load control dependency will not preserve ordering 91 have been applied. Therefore, if you need ordering in this example, 134 The compiler is therefore within its rights to transform the above code 144 is gone, and the barrier won't bring it back. Therefore, if you need 257 (*) Compilers do not understand control dependencies. It is therefore
|
/linux-6.12.1/Documentation/mm/ |
D | highmem.rst | 83 temporarily mapped. Therefore, users may call a plain page_address() 95 therefore try to design their code to avoid the use of kmap() by mapping 118 the issuing task is therefore required to stay on that CPU until it has 126 and disable pagefaults. This could be a source of unwanted latency. Therefore 149 available. Therefore, kmap() is only callable from preemptible context.
|
/linux-6.12.1/arch/arm64/kvm/hyp/nvhe/ |
D | sys_regs.c | 111 * No support for Scalable Vectors, therefore, hyp has no sanitized in get_pvm_id_aa64zfr0() 122 * therefore, pKVM has no sanitized copy of the feature id register. in get_pvm_id_aa64dfr0() 131 * No support for debug, therefore, hyp has no sanitized copy of the in get_pvm_id_aa64dfr1() 141 * No support for implementation defined features, therefore, hyp has no in get_pvm_id_aa64afr0() 151 * No support for implementation defined features, therefore, hyp has no in get_pvm_id_aa64afr1() 275 * No support for AArch32 guests, therefore, pKVM has no sanitized copy in pvm_access_id_aarch32()
|
/linux-6.12.1/arch/arm64/kvm/ |
D | inject_fault.c | 164 * VCPU therefore is not currently executing guest code. 180 * VCPU therefore is not currently executing guest code. 223 * VCPU therefore is not currently executing guest code. 244 * VCPU therefore is not currently executing guest code.
|
/linux-6.12.1/arch/arm/boot/dts/nxp/imx/ |
D | imx6qdl-dhcom-drc02.dtsi | 15 * Tx and Rx are routed to the DHCOM UART1 rts/cts pins. Therefore the micro SD 73 * DHCOM UART1 rts/cts pins. Therefore this UART have to use DHCOM GPIOs 119 * Therefore, they have been removed from the list below.
|
/linux-6.12.1/arch/x86/include/uapi/asm/ |
D | ldt.h | 19 * call is more for 32bit mode therefore. 34 * programs can pass uninitialized values here. Therefore, in
|
/linux-6.12.1/include/linux/platform_data/ |
D | i2c-gpio.h | 22 * Therefore disable open-drain. 27 * Therefore disable open-drain.
|
/linux-6.12.1/tools/arch/sparc/include/asm/ |
D | barrier_64.h | 10 * Therefore, if interrupts are disabled, the chip can hang forever. 24 * The branch has to be mispredicted for the bug to occur. Therefore, we put
|
/linux-6.12.1/Documentation/driver-api/ |
D | vfio-pci-device-specific-driver-acceptance.rst | 13 sustainable. The vfio-pci driver has therefore split out 26 New driver submissions are therefore requested to have approval via
|
D | vfio.rst | 67 Therefore, while for the most part an IOMMU may have device level 69 IOMMU API therefore supports a notion of IOMMU groups. A group is 71 system. Groups are therefore the unit of ownership used by VFIO. 126 This device is therefore in IOMMU group 26. This device is on the 127 pci bus, therefore the user will make use of vfio-pci to manage the 152 This device is behind a PCIe-to-PCI bridge [4]_, therefore we also 155 not currently have a host driver, therefore it's not required to 161 no capabilities on its own and is therefore expected to be set to 261 provide compatibility to the VFIO_SPAPR_TCE_IOMMU interface. Therefore 309 This device is therefore represented as vfio0. The user can verify
|
/linux-6.12.1/tools/power/cpupower/man/ |
D | cpupower-monitor.1 | 90 left. Therefore there can be some inaccuracy when cores are in an idle 126 The registers are accessed via PCI and therefore can still be read out while 133 Therefore this counter can be used to verify whether the graphics' driver
|
/linux-6.12.1/arch/sparc/include/asm/ |
D | barrier_64.h | 8 * Therefore, if interrupts are disabled, the chip can hang forever. 22 * The branch has to be mispredicted for the bug to occur. Therefore, we put
|
/linux-6.12.1/Documentation/ABI/testing/ |
D | sysfs-bus-surface_aggregator-tabletsw | 29 New states may be introduced with new hardware. Users therefore 55 New states may be introduced with new hardware. Users therefore
|
/linux-6.12.1/Documentation/RCU/Design/Requirements/ |
D | Requirements.rst | 27 This document therefore summarizes RCU's requirements, and can be 110 started after the synchronize_rcu() started, and must therefore also 111 load a value of one from ``x``. Therefore, the outcome: 249 optimizations could cause trouble. Therefore, we clearly need some way 570 | Therefore, there absolutely must be a full memory barrier between the | 646 guarantee. Therefore, the justification for adding a conditional 683 therefore all too easy to assume that RCU is guaranteeing more than it 805 | synchronize_rcu() completed. Therefore, the code following | 988 | Therefore, even in practice, RCU users must abide by the theoretical | 996 RCU implementation must abide by them. They therefore bear repeating: [all …]
|
/linux-6.12.1/include/linux/mtd/ |
D | xip.h | 27 * obviously not be running from flash. The __xipram is therefore marking 70 #warning "your system will therefore be unresponsive when writing or erasing flash"
|
/linux-6.12.1/Documentation/crypto/ |
D | intro.rst | 19 Therefore, a cipher handle variable usually has the name "tfm". Besides 68 returned to the consumer. Therefore, please refer to all initialization
|
/linux-6.12.1/drivers/scsi/pcmcia/ |
D | nsp_message.c | 21 * therefore we should poll the scsi phase here to catch in nsp_message_in() 62 * therefore we should poll the scsi phase here to catch in nsp_message_out()
|
12345678910>>...111