On Sat, Nov 3, 2018 at 11:04 AM, Thomas Gleixner wrote:
> Daniel,
>
> On Fri, 2 Nov 2018, Daniel Vacek wrote:
>> On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
>> >> -#define MAX_RETRIES 5
>> >> -#define SMI_TRESHOLD5
>> >> +#define MAX_RETRIES 5
>> >> +#define TSC_THRESHOLD
Daniel,
On Fri, 2 Nov 2018, Daniel Vacek wrote:
> On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
> >> -#define MAX_RETRIES 5
> >> -#define SMI_TRESHOLD5
> >> +#define MAX_RETRIES 5
> >> +#define TSC_THRESHOLD(tsc_khz >> 5)
> >
> > This breaks pit_hpet_ptimer_calibrate
Hi Thomas,
thanks for checking.
On Thu, Nov 1, 2018 at 4:34 PM, Thomas Gleixner wrote:
> Daniel,
>
> On Thu, 1 Nov 2018, Daniel Vacek wrote:
>
> Please use 'x86/tsc:' as prefix. git log path/to/file usually gives you a
> reasonable hint about prefixes.
Oh, sure thing. The dmesg always prints 't
Daniel,
On Thu, 1 Nov 2018, Daniel Vacek wrote:
Please use 'x86/tsc:' as prefix. git log path/to/file usually gives you a
reasonable hint about prefixes.
> -#define MAX_RETRIES 5
> -#define SMI_TRESHOLD5
> +#define MAX_RETRIES 5
> +#define TSC_THRESHOLD(tsc_khz >> 5)
This b
The threshold in tsc_read_refs() is constant which may favor slower CPUs
but may not be optimal for simple reading of reference on faster ones.
Hence make it proportional to tsc_khz to compensate for this. The threshold
guards against any disturbance like IRQs, NMIs, SMIs or CPU stealing by
host on
5 matches
Mail list logo