lkml.org 
[lkml]   [2019]   [Aug]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: setup_boot_APIC_clock() NULL dereference during early boot on reduced hardware platforms
On Thu, 1 Aug 2019, Li, Aubrey wrote:
> On 2019/8/1 16:13, Thomas Gleixner wrote:
> > The point is that it does not matter which vendor a CPU comes from. The
> > kernel does support legacyless boot when the frequencies are known. Whether
> > that's currently possible on that particular CPU is a different question.
> >
> Yeah, I should specify, Daniel, your platform needs a global clock event, ;-)

Care to look at the manuals before making assumptions?

2.1.9 Timers

Each core includes the following timers. These timers do not vary in
frequency regardless of the current P-state or C-state.

* Core::X86::Msr::TSC; the TSC increments at the rate specified by the
P0 Pstate. See Core::X86::Msr::PStateDef.

* The APIC timer (Core::X86::Apic::TimerInitialCount and
Core::X86::Apic::TimerCurrentCount), which increments at the rate of
2xCLKIN; the APIC timer may increment in units of between 1 and 8.

The Ryzens use a 100MHz input clock for the APIC normally, but I'm not sure
whether this is subject to overclocking. If so then it should be possible
to figure that out somehow. Tom?

Thanks,

tglx

\
 
 \ /
  Last update: 2019-08-01 12:14    [W:0.062 / U:1.624 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site