2021-05-05 10:37:39 -07:00
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2021 Intel Corporation
|
|
|
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
|
|
|
*/
|
2023-11-16 13:57:55 +02:00
|
|
|
|
|
|
|
|
#include <cpuid.h> /* Header provided by the toolchain. */
|
|
|
|
|
|
2023-08-28 13:15:43 +02:00
|
|
|
#include <zephyr/init.h>
|
2023-11-16 13:57:55 +02:00
|
|
|
#include <zephyr/arch/x86/cpuid.h>
|
2022-05-06 10:25:46 +02:00
|
|
|
#include <zephyr/drivers/timer/system_timer.h>
|
2026-07-03 07:45:26 +02:00
|
|
|
#include <zephyr/sys/clock.h>
|
2022-05-06 10:25:46 +02:00
|
|
|
#include <zephyr/drivers/interrupt_controller/loapic.h>
|
2022-10-17 10:24:11 +02:00
|
|
|
#include <zephyr/irq.h>
|
2021-05-05 10:37:39 -07:00
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
/*
|
|
|
|
|
* This driver is selected when either CONFIG_APIC_TIMER_TSC or
|
|
|
|
|
* CONFIG_APIC_TSC_DEADLINE_TIMER is selected. The later is preferred over
|
|
|
|
|
* the former when the TSC deadline comparator is available.
|
|
|
|
|
*/
|
|
|
|
|
BUILD_ASSERT((!IS_ENABLED(CONFIG_APIC_TIMER_TSC) &&
|
|
|
|
|
IS_ENABLED(CONFIG_APIC_TSC_DEADLINE_TIMER)) ||
|
|
|
|
|
(!IS_ENABLED(CONFIG_APIC_TSC_DEADLINE_TIMER) &&
|
|
|
|
|
IS_ENABLED(CONFIG_APIC_TIMER_TSC)),
|
|
|
|
|
"one of CONFIG_APIC_TIMER_TSC or CONFIG_APIC_TSC_DEADLINE_TIMER must be set");
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* If the TSC deadline comparator is not supported then the ICR in one-shot
|
|
|
|
|
* mode is used as a fallback method to trigger the next timeout interrupt.
|
|
|
|
|
* Those config symbols must then be defined:
|
|
|
|
|
*
|
|
|
|
|
* CONFIG_APIC_TIMER_TSC_N=<n>
|
|
|
|
|
* CONFIG_APIC_TIMER_TSC_M=<m>
|
|
|
|
|
*
|
|
|
|
|
* These are set to indicate the ratio of the TSC frequency to the local
|
|
|
|
|
* APIC timer frequency. This can be found via CPUID 0x15 (n = EBX, m = EAX)
|
|
|
|
|
* on most CPUs.
|
|
|
|
|
*/
|
|
|
|
|
#ifdef CONFIG_APIC_TIMER_TSC
|
|
|
|
|
#define APIC_TIMER_TSC_M CONFIG_APIC_TIMER_TSC_M
|
|
|
|
|
#define APIC_TIMER_TSC_N CONFIG_APIC_TIMER_TSC_N
|
|
|
|
|
#else
|
|
|
|
|
#define APIC_TIMER_TSC_M 1
|
|
|
|
|
#define APIC_TIMER_TSC_N 1
|
|
|
|
|
#endif
|
|
|
|
|
|
2021-05-05 10:37:39 -07:00
|
|
|
#define IA32_TSC_DEADLINE_MSR 0x6e0
|
|
|
|
|
#define IA32_TSC_ADJUST_MSR 0x03b
|
|
|
|
|
|
|
|
|
|
struct apic_timer_lvt {
|
|
|
|
|
uint8_t vector : 8;
|
|
|
|
|
uint8_t unused0 : 8;
|
|
|
|
|
uint8_t masked : 1;
|
|
|
|
|
enum { ONE_SHOT, PERIODIC, TSC_DEADLINE } mode: 2;
|
|
|
|
|
uint32_t unused2 : 13;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static union { uint32_t val; struct apic_timer_lvt lvt; } lvt_reg;
|
|
|
|
|
|
|
|
|
|
static ALWAYS_INLINE uint64_t rdtsc(void)
|
|
|
|
|
{
|
|
|
|
|
uint32_t hi, lo;
|
|
|
|
|
|
|
|
|
|
__asm__ volatile("rdtsc" : "=d"(hi), "=a"(lo));
|
|
|
|
|
return lo + (((uint64_t)hi) << 32);
|
|
|
|
|
}
|
|
|
|
|
|
2024-05-22 16:43:51 -04:00
|
|
|
static inline void wrmsr(int32_t msr, uint64_t val)
|
|
|
|
|
{
|
|
|
|
|
uint32_t hi = (uint32_t) (val >> 32);
|
|
|
|
|
uint32_t lo = (uint32_t) val;
|
|
|
|
|
|
|
|
|
|
__asm__ volatile("wrmsr" :: "d"(hi), "a"(lo), "c"(msr));
|
|
|
|
|
}
|
|
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
static void set_trigger(uint64_t deadline)
|
|
|
|
|
{
|
|
|
|
|
if (IS_ENABLED(CONFIG_APIC_TSC_DEADLINE_TIMER)) {
|
|
|
|
|
wrmsr(IA32_TSC_DEADLINE_MSR, deadline);
|
|
|
|
|
} else {
|
|
|
|
|
/* use the timer ICR to trigger next interrupt */
|
|
|
|
|
uint64_t curr_cycle = rdtsc();
|
|
|
|
|
uint64_t delta_cycles = deadline - MIN(deadline, curr_cycle);
|
|
|
|
|
uint64_t icr = (delta_cycles * APIC_TIMER_TSC_M) / APIC_TIMER_TSC_N;
|
|
|
|
|
|
|
|
|
|
/* cap icr to 32 bits, and not zero */
|
|
|
|
|
icr = CLAMP(icr, 1, UINT32_MAX);
|
|
|
|
|
x86_write_loapic(LOAPIC_TIMER_ICR, icr);
|
|
|
|
|
}
|
|
|
|
|
}
|
|
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
/*
|
|
|
|
|
* Free-running 64-bit TSC plus an absolute deadline (the TSC_DEADLINE MSR, or
|
|
|
|
|
* the local APIC timer ICR in one-shot mode as a fallback): a COMPARE_ORDERED
|
|
|
|
|
* backend. The TSC is 64 bits wide on a 32-bit build too, so the driver states
|
|
|
|
|
* that width instead of taking the native register default.
|
|
|
|
|
*/
|
|
|
|
|
#define TIMER_CORE_BACKEND_COMPARE_ORDERED
|
|
|
|
|
#define TIMER_CORE_COUNTER_WIDTH 64
|
2021-05-05 10:37:39 -07:00
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
static inline uint64_t timer_driver_cycle_get(void)
|
2021-05-05 10:37:39 -07:00
|
|
|
{
|
2026-07-22 17:00:52 -04:00
|
|
|
return rdtsc();
|
2021-05-05 10:37:39 -07:00
|
|
|
}
|
|
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
static inline void timer_driver_set_compare(uint64_t cycles)
|
2026-07-22 09:25:19 -04:00
|
|
|
{
|
2026-07-22 17:00:52 -04:00
|
|
|
set_trigger(cycles);
|
2026-07-22 09:25:19 -04:00
|
|
|
}
|
|
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
#include "system_timer_generic.h"
|
drivers: timer: apic_tsc: use the generic timer core
Convert the x86 APIC TSC timer to system_timer_generic.h. The free-running
64-bit TSC with an absolute deadline (the TSC_DEADLINE MSR, or the local
APIC timer ICR in one-shot mode as the fallback) is a COMPARE backend: the
driver keeps z_clock_cycle_get() (rdtsc) and z_clock_set_compare()
(set_trigger), and the core takes over the tick accounting, the deadline
math, the range clamp and the announce. The hand-rolled last_cycle
baseline and the sys_clock_elapsed() / set_timeout() tick math move into
the core; the ISR reduces to an announce, and smp_timer_init() keeps
copying CPU0's LVT to each secondary.
The frequency is a build-time constant here (this driver is not
runtime-frequency), so the core derives cycles-per-tick from
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC as before. CYCLES_WIDTH defaults to the
unsigned long width, matching the driver's former native-register divisor.
The deadline arm range narrows from the driver's former three-quarter
span to the core's default half span. Half the span reserves the upper
half as IRQ-latency headroom, so a late announce of a maximum-length arm
still yields an in-range delta; the three-quarter bound did not keep that
margin. The realistic tick range is far below either bound, so this is not
a functional change.
The one dropped behaviour is the set_timeout() guard that pinned a deadline
to UINT64_MAX when the computed deadline wrapped the 64-bit TSC: it guarded
an unreachable, untestable case (the 64-bit TSC takes centuries to wrap,
about 585 years at 1 GHz) and has no clean place in the core, whose range
clamp already bounds the realistic range.
Build-verified on qemu_x86_64 and qemu_x86 (the 64- and 32-bit unsigned
long paths) with the TSC deadline comparator, and on qemu_x86_64 with the
APIC_TIMER_TSC ICR fallback. No QEMU target runs this driver (qemu_x86*
default to HPET, and forcing the TSC timer on QEMU's atom model delivers no
deadline interrupts, on mainline too), so this is a build-only conversion;
its real users are ACRN and x86 hardware.
Signed-off-by: Nicolas Pitre <npitre@baylibre.com>
2026-07-07 17:22:46 -04:00
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
static void isr(const void *arg)
|
2026-07-22 09:25:19 -04:00
|
|
|
{
|
2026-07-22 17:00:52 -04:00
|
|
|
ARG_UNUSED(arg);
|
|
|
|
|
|
|
|
|
|
timer_core_announce();
|
2021-10-29 20:10:35 -04:00
|
|
|
}
|
|
|
|
|
|
2021-05-05 10:37:39 -07:00
|
|
|
static inline uint32_t timer_irq(void)
|
|
|
|
|
{
|
|
|
|
|
/* The Zephyr APIC API is... idiosyncratic. The timer is a
|
|
|
|
|
* "local vector table" interrupt. These aren't system IRQs
|
|
|
|
|
* presented to the IO-APIC, they're indices into a register
|
|
|
|
|
* array in the local APIC. By Zephyr convention they come
|
|
|
|
|
* after all the external IO-APIC interrupts, but that number
|
|
|
|
|
* changes depending on device configuration so we have to
|
|
|
|
|
* fetch it at runtime. The timer happens to be the first
|
|
|
|
|
* entry in the table.
|
|
|
|
|
*/
|
|
|
|
|
return z_loapic_irq_base();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* The TSC_ADJUST MSR implements a synchronized offset such that
|
|
|
|
|
* multiple CPUs (within a socket, anyway) can synchronize exactly, or
|
|
|
|
|
* implement managed timing spaces for guests in a recoverable way,
|
|
|
|
|
* etc... We set it to zero on all cores for simplicity, because
|
|
|
|
|
* firmware often leaves it in an inconsistent state between cores.
|
|
|
|
|
*/
|
|
|
|
|
static void clear_tsc_adjust(void)
|
|
|
|
|
{
|
|
|
|
|
/* But don't touch it on ACRN, where an hypervisor bug
|
|
|
|
|
* confuses the APIC emulation and deadline interrupts don't
|
|
|
|
|
* arrive.
|
|
|
|
|
*/
|
|
|
|
|
#ifndef CONFIG_BOARD_ACRN
|
|
|
|
|
wrmsr(IA32_TSC_ADJUST_MSR, 0);
|
|
|
|
|
#endif
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void smp_timer_init(void)
|
|
|
|
|
{
|
|
|
|
|
/* Copy the LVT configuration from CPU0, because IRQ_CONNECT()
|
|
|
|
|
* doesn't know how to manage LVT interrupts for anything
|
|
|
|
|
* other than the calling/initial CPU. Same fence needed to
|
|
|
|
|
* prevent later MSR writes from reordering before the APIC
|
|
|
|
|
* configuration write.
|
|
|
|
|
*/
|
|
|
|
|
x86_write_loapic(LOAPIC_TIMER, lvt_reg.val);
|
|
|
|
|
__asm__ volatile("mfence" ::: "memory");
|
|
|
|
|
clear_tsc_adjust();
|
|
|
|
|
irq_enable(timer_irq());
|
|
|
|
|
}
|
|
|
|
|
|
init: remove the need for a dummy device pointer in SYS_INIT functions
The init infrastructure, found in `init.h`, is currently used by:
- `SYS_INIT`: to call functions before `main`
- `DEVICE_*`: to initialize devices
They are all sorted according to an initialization level + a priority.
`SYS_INIT` calls are really orthogonal to devices, however, the required
function signature requires a `const struct device *dev` as a first
argument. The only reason for that is because the same init machinery is
used by devices, so we have something like:
```c
struct init_entry {
int (*init)(const struct device *dev);
/* only set by DEVICE_*, otherwise NULL */
const struct device *dev;
}
```
As a result, we end up with such weird/ugly pattern:
```c
static int my_init(const struct device *dev)
{
/* always NULL! add ARG_UNUSED to avoid compiler warning */
ARG_UNUSED(dev);
...
}
```
This is really a result of poor internals isolation. This patch proposes
a to make init entries more flexible so that they can accept sytem
initialization calls like this:
```c
static int my_init(void)
{
...
}
```
This is achieved using a union:
```c
union init_function {
/* for SYS_INIT, used when init_entry.dev == NULL */
int (*sys)(void);
/* for DEVICE*, used when init_entry.dev != NULL */
int (*dev)(const struct device *dev);
};
struct init_entry {
/* stores init function (either for SYS_INIT or DEVICE*)
union init_function init_fn;
/* stores device pointer for DEVICE*, NULL for SYS_INIT. Allows
* to know which union entry to call.
*/
const struct device *dev;
}
```
This solution **does not increase ROM usage**, and allows to offer clean
public APIs for both SYS_INIT and DEVICE*. Note that however, init
machinery keeps a coupling with devices.
**NOTE**: This is a breaking change! All `SYS_INIT` functions will need
to be converted to the new signature. See the script offered in the
following commit.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
init: convert SYS_INIT functions to the new signature
Conversion scripted using scripts/utils/migrate_sys_init.py.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
manifest: update projects for SYS_INIT changes
Update modules with updated SYS_INIT calls:
- hal_ti
- lvgl
- sof
- TraceRecorderSource
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: devicetree: devices: adjust test
Adjust test according to the recently introduced SYS_INIT
infrastructure.
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
tests: kernel: threads: adjust SYS_INIT call
Adjust to the new signature: int (*init_fn)(void);
Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-10-19 09:33:44 +02:00
|
|
|
static int sys_clock_driver_init(void)
|
2021-05-05 10:37:39 -07:00
|
|
|
{
|
2024-05-06 11:02:27 +02:00
|
|
|
#ifdef CONFIG_ASSERT
|
2021-05-05 10:37:39 -07:00
|
|
|
uint32_t eax, ebx, ecx, edx;
|
|
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
if (IS_ENABLED(CONFIG_APIC_TSC_DEADLINE_TIMER)) {
|
|
|
|
|
ecx = 0; /* prevent compiler warning */
|
|
|
|
|
__get_cpuid(CPUID_BASIC_INFO_1, &eax, &ebx, &ecx, &edx);
|
|
|
|
|
__ASSERT((ecx & BIT(24)) != 0, "No TSC Deadline support");
|
|
|
|
|
}
|
2021-05-05 10:37:39 -07:00
|
|
|
|
2023-11-16 13:57:55 +02:00
|
|
|
edx = 0; /* prevent compiler warning */
|
|
|
|
|
__get_cpuid(0x80000007, &eax, &ebx, &ecx, &edx);
|
2021-05-05 10:37:39 -07:00
|
|
|
__ASSERT((edx & BIT(8)) != 0, "No Invariant TSC support");
|
|
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
if (IS_ENABLED(CONFIG_SMP)) {
|
|
|
|
|
ebx = 0; /* prevent compiler warning */
|
|
|
|
|
__get_cpuid_count(CPUID_EXTENDED_FEATURES_LVL, 0, &eax, &ebx, &ecx, &edx);
|
|
|
|
|
__ASSERT((ebx & BIT(1)) != 0, "No TSC_ADJUST MSR support");
|
|
|
|
|
}
|
2021-05-05 10:37:39 -07:00
|
|
|
#endif
|
|
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
if (IS_ENABLED(CONFIG_SMP)) {
|
|
|
|
|
clear_tsc_adjust();
|
|
|
|
|
}
|
2021-05-05 10:37:39 -07:00
|
|
|
|
|
|
|
|
/* Timer interrupt number is runtime-fetched, so can't use
|
|
|
|
|
* static IRQ_CONNECT()
|
|
|
|
|
*/
|
|
|
|
|
irq_connect_dynamic(timer_irq(), CONFIG_APIC_TIMER_IRQ_PRIORITY, isr, 0, 0);
|
|
|
|
|
|
2024-05-23 17:27:18 -04:00
|
|
|
if (IS_ENABLED(CONFIG_APIC_TIMER_TSC)) {
|
|
|
|
|
uint32_t timer_conf;
|
|
|
|
|
|
|
|
|
|
timer_conf = x86_read_loapic(LOAPIC_TIMER_CONFIG);
|
|
|
|
|
timer_conf &= ~0x0f; /* clear divider bits */
|
|
|
|
|
timer_conf |= 0x0b; /* divide by 1 */
|
|
|
|
|
x86_write_loapic(LOAPIC_TIMER_CONFIG, timer_conf);
|
|
|
|
|
}
|
|
|
|
|
|
2021-05-05 10:37:39 -07:00
|
|
|
lvt_reg.val = x86_read_loapic(LOAPIC_TIMER);
|
2024-05-23 17:27:18 -04:00
|
|
|
lvt_reg.lvt.mode = IS_ENABLED(CONFIG_APIC_TSC_DEADLINE_TIMER) ?
|
|
|
|
|
TSC_DEADLINE : ONE_SHOT;
|
2021-05-05 10:37:39 -07:00
|
|
|
lvt_reg.lvt.masked = 0;
|
|
|
|
|
x86_write_loapic(LOAPIC_TIMER, lvt_reg.val);
|
|
|
|
|
|
|
|
|
|
/* Per the SDM, the TSC_DEADLINE MSR is not serializing, so
|
|
|
|
|
* this fence is needed to be sure that an upcoming MSR write
|
|
|
|
|
* (i.e. a timeout we're about to set) cannot possibly reorder
|
|
|
|
|
* around the initialization we just did.
|
|
|
|
|
*/
|
|
|
|
|
__asm__ volatile("mfence" ::: "memory");
|
|
|
|
|
|
2026-07-22 17:00:52 -04:00
|
|
|
timer_core_init();
|
2024-05-22 16:43:51 -04:00
|
|
|
irq_enable(timer_irq());
|
2021-05-05 10:37:39 -07:00
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
|
}
|
2021-11-04 12:51:39 +01:00
|
|
|
|
|
|
|
|
SYS_INIT(sys_clock_driver_init, PRE_KERNEL_2,
|
|
|
|
|
CONFIG_SYSTEM_CLOCK_INIT_PRIORITY);
|