/kernel/linux/linux-5.10/Documentation/virt/kvm/ |
D | timekeeping.rst | 14 3) TSC Hardware 37 First we discuss the basic hardware devices available. TSC and the related 324 3. TSC Hardware 327 The TSC or time stamp counter is relatively simple in theory; it counts 332 The TSC is represented internally as a 64-bit MSR which can be read with the 334 limitations made it possible to write the TSC, but generally on old hardware it 339 write the TSC MSR is not an architectural guarantee. 341 The TSC is accessible from CPL-0 and conditionally, for CPL > 0 software by 342 means of the CR4.TSD bit, which when enabled, disables CPL > 0 TSC access. 345 atomically not just the TSC, but an indicator which corresponds to the [all …]
|
D | hypercalls.rst | 130 * tsc: guest TSC value used to calculate sec/nsec pair 134 host and guest. The guest can use the returned TSC value to 137 Returns KVM_EOPNOTSUPP if the host does not use TSC clocksource,
|
D | api.rst | 973 TSC is not stable. 1644 The TSC deadline timer feature (CPUID leaf 1, ecx[24]) is always returned
|
/kernel/linux/linux-5.10/tools/power/cpupower/utils/idle_monitor/ |
D | nhm_idle.c | 27 enum intel_nhm_id { C3 = 0, C6, PC3, PC6, TSC = 0xFFFF }; enumerator 89 case TSC: in nhm_get_count() 131 nhm_get_count(TSC, &tsc_at_measure_start, base_cpu); in nhm_start() 139 nhm_get_count(TSC, &dbg, base_cpu); in nhm_start() 150 nhm_get_count(TSC, &tsc_at_measure_end, base_cpu); in nhm_stop() 158 nhm_get_count(TSC, &dbg, base_cpu); in nhm_stop()
|
D | snb_idle.c | 24 enum intel_snb_id { C7 = 0, PC2, PC7, SNB_CSTATE_COUNT, TSC = 0xFFFF }; enumerator 75 case TSC: in snb_get_count() 122 snb_get_count(TSC, &tsc_at_measure_start, base_cpu); in snb_start() 131 snb_get_count(TSC, &tsc_at_measure_end, base_cpu); in snb_stop()
|
D | hsw_ext_idle.c | 26 TSC = 0xFFFF }; enumerator 77 case TSC: in hsw_ext_get_count() 124 hsw_ext_get_count(TSC, &tsc_at_measure_start, base_cpu); in hsw_ext_start() 133 hsw_ext_get_count(TSC, &tsc_at_measure_end, base_cpu); in hsw_ext_stop()
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/touchscreen/ |
D | lpc32xx-tsc.txt | 1 * NXP LPC32xx SoC Touchscreen Controller (TSC) 7 - interrupts: The TSC/ADC interrupt
|
D | ti-tsc-adc.txt | 1 * TI - TSC ADC (Touschscreen and analog digital converter)
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
D | fsl-imx25-tsadc.txt | 1 Freescale MX25 ADC/TSC MultiFunction Device (MFD)
|
/kernel/linux/linux-5.10/tools/perf/Documentation/ |
D | perf-intel-pt.txt | 237 So, to disable TSC packets use: 290 tsc Always supported. Produces TSC timestamp packets to provide 342 Because a TSC packet is produced with PSB, the PSB period can 348 MTC packets provide finer grain timestamp information than TSC 350 clock (CTC) which is related to TSC packets using a TMA packet. 379 can be related to TSC via values provided in cpuid leaf 0x15. 393 MTC and TSC packets. A CYC packet contains the number of CPU 394 cycles since the last CYC packet. Unlike MTC and TSC packets, 832 Note also, the sched_switch event is only added if TSC packets are requested. 943 "ns" (nanoseconds), "t" (TSC ticks) or "i" (instructions). [all …]
|
D | jitdump-specification.txt | 49 …g an architecture-specific timestamp clock source. For instance, on x86, one could use TSC directly
|
/kernel/linux/linux-5.10/arch/x86/ |
D | Kconfig.cpu | 24 - "586" for generic Pentium CPUs lacking the TSC 187 like a 586 with TSC, and sets some GCC optimization flags (like a 201 treat this chip as a 586TSC with some extended instructions 209 treat this chip as a 586TSC with some extended instructions
|
D | Kconfig | 871 systems, unlike the TSC, but it is more expensive to access, 893 systems, unlike the TSC, but it is more expensive to access, 2792 NSC Geode SC-1100's buggy TSC, which loses time when the
|
/kernel/linux/linux-5.10/Documentation/trace/ |
D | hwlat_detector.rst | 26 for some period, then looking for gaps in the TSC data. Any gap indicates a
|
/kernel/linux/linux-5.10/kernel/time/ |
D | Kconfig | 21 # cycle update - x86/TSC misfeature
|
/kernel/linux/linux-5.10/drivers/net/wireless/admtek/ |
D | adm8211.h | 64 __le32 TSC; /* 0xC0 CSR32 */ member
|
/kernel/linux/linux-5.10/arch/x86/kvm/ |
D | cpuid.c | 383 F(TSC) | F(MSR) | F(PAE) | F(MCE) | in kvm_set_cpu_caps() 453 F(TSC) | F(MSR) | F(PAE) | F(MCE) | in kvm_set_cpu_caps()
|
/kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/apei/ |
D | einj.rst | 179 [22715.834759] EDAC sbridge MC3: TSC 0
|
/kernel/linux/linux-5.10/arch/arm/boot/dts/ |
D | lpc32xx.dtsi | 433 * TSC vs. ADC: Since those two share the same
|
/kernel/linux/linux-5.10/drivers/input/touchscreen/ |
D | Kconfig | 897 - DMC TSC-10/25 976 bool "DMC TSC-10/25 device support" if EXPERT 1065 tristate "TSC-10/25/40 serial touchscreen support" 1068 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
|
/kernel/linux/linux-5.10/Documentation/timers/ |
D | timekeeping.rst | 154 Some hardware (such as the x86 TSC) will cause the sched_clock() function to
|
/kernel/linux/linux-5.10/drivers/acpi/ |
D | Kconfig | 537 (TSC) timing source.
|
/kernel/linux/linux-5.10/Documentation/ABI/testing/ |
D | sysfs-devices-system-cpu | 591 in TSC-quanta that the CPU can reside in either C0.1
|
/kernel/linux/linux-5.10/Documentation/admin-guide/ |
D | kernel-parameters.txt | 2441 lapic= [X86,APIC] Do not use TSC deadline 5534 tsc= Disable clocksource stability checks for TSC. 5541 [x86] noirqtime: Do not use TSC to do irq accounting. 5545 [x86] unstable: mark the TSC clocksource as unstable, this 5546 marks the TSC unconditionally unstable at bootup and 5547 avoids any further wobbles once the TSC watchdog notices. 5553 tsc_early_khz= [X86] Skip early TSC calibration and use the given 5554 value instead. Useful when the early TSC frequency discovery
|
/kernel/linux/linux-5.10/arch/x86/kvm/vmx/ |
D | vmx.c | 7256 cr4_fixed1_update(X86_CR4_TSD, edx, feature_bit(TSC)); in nested_vmx_cr_fixed1_bits_update()
|