> >> If we determined tsc early in boot using one of the quick methods:
> >> from cpuid/msr/quick_pit, can we assume that frequencies of all other
> >> CPUs will be determined the same way? Or do we still have to fallback
Not on 32bit at least. You can have a mixed slot 1 SMP system such as
an ASU
On 07/19/2018 04:44 PM, Thomas Gleixner wrote:
> On Thu, 19 Jul 2018, Pavel Tatashin wrote:
>
>> On Thu, Jul 19, 2018 at 12:49 PM Pavel Tatashin
>> wrote:
>>>
So create two functions. native_...early..() and native(). The early
one does not contain the hpet/pmtimer stuff and it r
On Thu, 19 Jul 2018, Pavel Tatashin wrote:
> On Thu, Jul 19, 2018 at 12:49 PM Pavel Tatashin
> wrote:
> >
> > > So create two functions. native_...early..() and native(). The early
> > > one does not contain the hpet/pmtimer stuff and it replaces the
> > > ops.pointer
> > > with the late one
On Thu, Jul 19, 2018 at 12:49 PM Pavel Tatashin
wrote:
>
> > So create two functions. native_...early..() and native(). The early
> > one does not contain the hpet/pmtimer stuff and it replaces the ops.pointer
> > with the late one which contains all of it.
>
> Good idea. Actually, the late on
> So create two functions. native_...early..() and native(). The early
> one does not contain the hpet/pmtimer stuff and it replaces the ops.pointer
> with the late one which contains all of it.
Good idea. Actually, the late one will contain only hpet/pmtimer and I
will set it only if tsc freq
On Thu, 19 Jul 2018, Pavel Tatashin wrote:
> On 07/19/2018 07:01 AM, Thomas Gleixner wrote:
>
> And hpet_pmtime_calibrate_cpu() contains all the hpet/pmtime stuff.
>
> However, when cpu_khz = x86_platform.calibrate_cpu() is called the first
> time, we still call hpet_pmtime_calibrate_cpu() from
>
On 07/19/2018 07:01 AM, Thomas Gleixner wrote:
> On Thu, 19 Jul 2018, Peter Zijlstra wrote:
>> On Tue, Jul 17, 2018 at 10:22:06PM -0400, Pavel Tatashin wrote:
>>> During boot tsc is calibrated twice: once in tsc_early_delay_calibrate(),
>>> and the second time in tsc_init().
>>>
>>> Rename tsc_e
On Thu, 19 Jul 2018, Peter Zijlstra wrote:
> On Tue, Jul 17, 2018 at 10:22:06PM -0400, Pavel Tatashin wrote:
> > During boot tsc is calibrated twice: once in tsc_early_delay_calibrate(),
> > and the second time in tsc_init().
> >
> > Rename tsc_early_delay_calibrate() to tsc_early_init(), and rewo
On Tue, Jul 17, 2018 at 10:22:06PM -0400, Pavel Tatashin wrote:
> During boot tsc is calibrated twice: once in tsc_early_delay_calibrate(),
> and the second time in tsc_init().
>
> Rename tsc_early_delay_calibrate() to tsc_early_init(), and rework it so
> the calibration is done only early, and ma
Hi Thomas,
At 07/19/2018 02:25 PM, Thomas Gleixner wrote:
On Thu, 19 Jul 2018, Dou Liyang wrote:
At 07/18/2018 10:22 AM, Pavel Tatashin wrote:
+ (unsigned long)cpu_khz % KHZ);
if (cpu_khz != tsc_khz) {
pr_info("Detected %lu.%03lu MHz TSC",
-
On Thu, 19 Jul 2018, Dou Liyang wrote:
> At 07/18/2018 10:22 AM, Pavel Tatashin wrote:
> > + (unsigned long)cpu_khz % KHZ);
> > if (cpu_khz != tsc_khz) {
> > pr_info("Detected %lu.%03lu MHz TSC",
> > - (unsigned long)tsc_khz / 1000,
> > -
Hi, Pavel
I am sorry, I didn't point out typo clearly in the previous version.
Please see the concerns below. ;-)
At 07/18/2018 10:22 AM, Pavel Tatashin wrote:
During boot tsc is calibrated twice: once in tsc_early_delay_calibrate(),
and the second time in tsc_init().
Rename tsc_early_delay_ca
During boot tsc is calibrated twice: once in tsc_early_delay_calibrate(),
and the second time in tsc_init().
Rename tsc_early_delay_calibrate() to tsc_early_init(), and rework it so
the calibration is done only early, and make tsc_init() to use the values
already determined in tsc_early_init().
S
13 matches
Mail list logo