From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Pavel Tatashin <pasha.tatashin@oracle.com>
Cc: Steve Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
<linux@armlinux.org.uk>, <schwidefsky@de.ibm.com>,
<heiko.carstens@de.ibm.com>, John Stultz <john.stultz@linaro.org>,
<sboyd@codeaurora.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, <hpa@zytor.com>
Subject: Re: [PATCH v8 6/6] x86/tsc: use tsc early
Date: Wed, 15 Nov 2017 11:53:07 +0800 [thread overview]
Message-ID: <6813baaf-909e-e32e-b074-6c466ceabcc6@cn.fujitsu.com> (raw)
In-Reply-To: <CAOAebxvVba7h6eq8P6iHwvTm6XAyb85cKyff1UOW+xhF52L=Dw@mail.gmail.com>
Hi Pavel,
At 11/15/2017 05:46 AM, Pavel Tatashin wrote:
> Hi Dou,
>
> Great comments, my replies below:
>
>>> static inline unsigned long long paravirt_sched_clock(void)
>>> {
>>> - return PVOP_CALL0(unsigned long long, pv_time_ops.sched_clock);
>>> + return PVOP_CALL0(unsigned long long,
>>> pv_time_ops.active_sched_clock);
>>> }
>>>
>>
>> Should in the 5th patch
>
> Actually, it has to be in patch 6, because otherwise patch 5 without
> patch 6 would cause native_sched_clock() to be used even when a
> platform specific clock is set, thus may cause performance regressions
> where it is not optimal to use tsc for clock.
>
Indeed.
>> + tsc_early_disable();
>> + __sched_clock_offset = sched_clock_early() - sched_clock();
>> + pr_info("sched clock early is finished, offset[%lld.%09lds]\n", t, r);
>> +}
s/sched clock early/early sched clock/
>> +#endif /* CONFIG_X86_TSC */
>> Add definitions for the situation of X86_TSC = no :
>>
>> #else /* CONFIG_X86_TSC */
>> static inline void tsc_early_init(unsigned int khz) { }
>> static inline void tsc_early_fini(void) { }
>
> Excellent point, I totally forgot about X86_TSC = no, however, a
> better fix is to simply remove #ifdef CONFIG_X86_TSC from my
> functions. Apparently, even with X86_TSC=no we can use TSC unless
Agree with removing #ifdef CONFIG_X86_TSC
> notsc kernel parameter is passed. This will be in the next patchset.
>
>>
>> According to tsc_early_delay_calibrate(), if (!boot_cpu_has(X86_FEATURE_TSC
>> || !tsc_khz ), tsc_early_init(tsc_khz)
>> will never be called, so here is redundant.
>>
>>> return;
>>> }
>>>
>>> @@ -1302,6 +1385,7 @@ void __init tsc_init(void)
>>> if (!tsc_khz) {
>>> mark_tsc_unstable("could not calculate TSC khz");
>>> setup_clear_cpu_cap(X86_FEATURE_TSC_DEADLINE_TIMER);
>>> + tsc_early_fini();
>>
>>
>> ditto
>
> Right, in both case we still want to call tsc_early_fini(). Because,
> it calls tsc_early_disable() even when tsc_early_init() was never
> called. tsc_early_disable() either sets static branch
> __tsc_early_static to false or changes active_sched_clock to be
> platform specific, depending on CONFIG_PARAVIRT.
Yes, the function names confused me, the actually purpose of
tsc_early_fini() is switching schedule clock to the final one. right?
How about replacing *return;* with *goto final_sched_clock;*
Thanks,
dou.
>
>> BTW, seems you forgot to cc Peter Zijlstra <peterz@infradead.org> in both V7
>> and V8 patchsets.
>
> Thank you for noticing this! I will include Peter when I send out
> patchset version 9.
>
> Thank you,
> Pavel
>
>
>
next prev parent reply other threads:[~2017-11-15 3:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 3:01 [PATCH v8 0/6] Early boot time stamps for x86 Pavel Tatashin
2017-11-09 3:01 ` [PATCH v8 1/6] x86/tsc: remove tsc_disabled flag Pavel Tatashin
2017-11-13 3:52 ` Dou Liyang
2017-11-13 18:51 ` Pavel Tatashin
2017-11-09 3:01 ` [PATCH v8 2/6] time: sync read_boot_clock64() with persistent clock Pavel Tatashin
2017-11-13 3:47 ` Dou Liyang
2017-11-14 19:57 ` Pavel Tatashin
2017-11-15 2:47 ` Dou Liyang
2017-11-15 3:56 ` Pavel Tatashin
2017-11-09 3:01 ` [PATCH v8 3/6] x86/time: read_boot_clock64() implementation Pavel Tatashin
2017-11-09 3:01 ` [PATCH v8 4/6] sched: early boot clock Pavel Tatashin
2017-11-09 3:02 ` [PATCH v8 5/6] x86/paravirt: add active_sched_clock to pv_time_ops Pavel Tatashin
2017-11-09 3:02 ` [PATCH v8 6/6] x86/tsc: use tsc early Pavel Tatashin
2017-11-13 3:47 ` Dou Liyang
2017-11-14 21:46 ` Pavel Tatashin
2017-11-15 3:53 ` Dou Liyang [this message]
2017-11-15 16:01 ` Pavel Tatashin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6813baaf-909e-e32e-b074-6c466ceabcc6@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=daniel.m.jordan@oracle.com \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=pasha.tatashin@oracle.com \
--cc=sboyd@codeaurora.org \
--cc=schwidefsky@de.ibm.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®