From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, Andy Lutomirski <luto@amacapital.net>,
Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86: Kill notsc
Date: Wed, 21 Oct 2015 21:01:09 +0200 [thread overview]
Message-ID: <20151021190109.GC2508@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20151021175803.GF3575@pd.tnic>
On Wed, Oct 21, 2015 at 07:58:03PM +0200, Borislav Petkov wrote:
> > +#ifdef CONFIG_X86_TSC
> > + /* return the value in ns */
> > + return cycles_2_ns(rdtsc());
> > +#else
>
> Ok, we have a problem here:
>
> See the splat below. On the init path
>
> start_kernel
> |-> sched_init
> |-> init_idle
>
> we're calling sched_clock() which does the cycles_2_ns() thing.
>
> However, that cycles_2_ns() thing gets called only in tsc_init() which
> comes later in start_kernel().
>
> Which means, data in this line
>
> ns += mul_u64_u32_shr(cyc, data->cyc2ns_mul, data->cyc2ns_shift);
>
> is NULL.
>
> Now, the question is, can I push only the cyc2ns_init() call up, before
> sched_init()?
I _think_ so, but its late. It would result in sched_clock() being 0
until you hit that other bit, but that should be fine (maybe).
next prev parent reply other threads:[~2015-10-21 19:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 14:20 Borislav Petkov
2015-10-19 4:47 ` Andy Lutomirski
2015-10-19 8:16 ` Borislav Petkov
2015-10-21 17:58 ` Borislav Petkov
2015-10-21 19:01 ` Peter Zijlstra [this message]
2015-10-22 18:51 ` [PATCH -v2] " Borislav Petkov
2015-11-04 10:21 ` Thomas Gleixner
2015-11-04 10:29 ` Borislav Petkov
2015-11-16 18:45 ` [RFC PATCH -v2.1] " Borislav Petkov
2015-11-16 21:25 ` Thomas Gleixner
2015-11-17 5:02 ` H. Peter Anvin
2015-11-17 8:53 ` Borislav Petkov
2015-11-17 9:11 ` Thomas Gleixner
2015-11-17 9:33 ` Borislav Petkov
2015-11-17 10:08 ` Thomas Gleixner
2015-11-17 11:09 ` Borislav Petkov
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=20151021190109.GC2508@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rostedt@goodmis.org \
--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
Powered by JetHome