| /Linux-v5.4/Documentation/virt/kvm/ |
| D | timekeeping.txt | 9 3) TSC Hardware
34 First we discuss the basic hardware devices available. TSC and the related
312 3) TSC Hardware
314 The TSC or time stamp counter is relatively simple in theory; it counts
319 The TSC is represented internally as a 64-bit MSR which can be read with the
321 limitations made it possible to write the TSC, but generally on old hardware it
326 write the TSC MSR is not an architectural guarantee.
328 The TSC is accessible from CPL-0 and conditionally, for CPL > 0 software by
329 means of the CR4.TSD bit, which when enabled, disables CPL > 0 TSC access.
332 atomically not just the TSC, but an indicator which corresponds to the
[all …]
|
| D | hypercalls.txt | 115 * tsc: guest TSC value used to calculate sec/nsec pair
119 host and guest. The guest can use the returned TSC value to
122 Returns KVM_EOPNOTSUPP if the host does not use TSC clocksource,
|
| /Linux-v5.4/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 | hsw_ext_idle.c | 26 TSC = 0xFFFF }; enumerator
78 case TSC: in hsw_ext_get_count()
125 hsw_ext_get_count(TSC, &tsc_at_measure_start, base_cpu); in hsw_ext_start()
134 hsw_ext_get_count(TSC, &tsc_at_measure_end, base_cpu); in hsw_ext_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()
|
| /Linux-v5.4/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)
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | rcar-gen3-thermal.txt | 3 On R-Car Gen3 SoCs, the thermal sensor controllers (TSC) control the thermal
24 - interrupts : interrupts routed to the TSC (must be 3).
|
| /Linux-v5.4/Documentation/devicetree/bindings/mfd/ |
| D | fsl-imx25-tsadc.txt | 1 Freescale MX25 ADC/TSC MultiFunction Device (MFD)
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/adc/ |
| D | amlogic,meson-saradc.txt | 28 of the TSC (temperature sensor coefficient) on
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | intel-pt.txt | 202 So, to disable TSC packets use:
255 tsc Always supported. Produces TSC timestamp packets to provide
307 Because a TSC packet is produced with PSB, the PSB period can
313 MTC packets provide finer grain timestamp information than TSC
315 clock (CTC) which is related to TSC packets using a TMA packet.
344 can be related to TSC via values provided in cpuid leaf 0x15.
358 MTC and TSC packets. A CYC packet contains the number of CPU
359 cycles since the last CYC packet. Unlike MTC and TSC packets,
725 Note also, the sched_switch event is only added if TSC packets are requested.
820 "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
|
| /Linux-v5.4/arch/x86/ |
| D | Kconfig.cpu | 24 - "586" for generic Pentium CPUs lacking the TSC
180 like a 586 with TSC, and sets some GCC optimization flags (like a
194 treat this chip as a 586TSC with some extended instructions
202 treat this chip as a 586TSC with some extended instructions
|
| /Linux-v5.4/kernel/time/ |
| D | Kconfig | 21 # cycle update - x86/TSC misfeature
|
| /Linux-v5.4/Documentation/trace/ |
| D | hwlat_detector.rst | 26 for some period, then looking for gaps in the TSC data. Any gap indicates a
|
| /Linux-v5.4/drivers/net/wireless/admtek/ |
| D | adm8211.h | 64 __le32 TSC; /* 0xC0 CSR32 */ member
|
| /Linux-v5.4/arch/x86/kvm/ |
| D | cpuid.c | 449 F(TSC) | F(MSR) | F(PAE) | F(MCE) | in __do_cpuid_func()
459 F(TSC) | F(MSR) | F(PAE) | F(MCE) | in __do_cpuid_func()
|
| /Linux-v5.4/Documentation/firmware-guide/acpi/apei/ |
| D | einj.rst | 179 [22715.834759] EDAC sbridge MC3: TSC 0
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | lpc32xx.dtsi | 436 * TSC vs. ADC: Since those two share the same
|
| /Linux-v5.4/drivers/input/touchscreen/ |
| D | Kconfig | 885 - DMC TSC-10/25
964 bool "DMC TSC-10/25 device support" if EXPERT
1054 tristate "TSC-10/25/40 serial touchscreen support"
1057 Say Y here if you have a TSC-10, 25 or 40 serial touchscreen connected
|
| /Linux-v5.4/Documentation/timers/ |
| D | timekeeping.rst | 154 Some hardware (such as the x86 TSC) will cause the sched_clock() function to
|
| /Linux-v5.4/drivers/acpi/ |
| D | Kconfig | 592 (TSC) timing source.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-system-cpu | 563 in TSC-quanta that the CPU can reside in either C0.1
|
| /Linux-v5.4/Documentation/virt/uml/ |
| D | UserModeLinux-HOWTO.txt | 4013 to calculate the BogoMips rating, using the TSC if it's there or using
4014 a one-instruction loop. The TSC produces twice the BogoMips as the
4015 loop. UML uses the loop, since it has nothing resembling a TSC, and
4017 However, on a host with a TSC, its BogoMips will be double the loop
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 2209 lapic= [x86,APIC] "notscdeadline" Do not use TSC deadline
4859 tsc= Disable clocksource stability checks for TSC.
4866 [x86] noirqtime: Do not use TSC to do irq accounting.
4870 [x86] unstable: mark the TSC clocksource as unstable, this
4871 marks the TSC unconditionally unstable at bootup and
4872 avoids any further wobbles once the TSC watchdog notices.
|
