From: Feng Tang <feng.tang@intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Petr Mladek <pmladek@suse.com>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alek.du@intel.com
Subject: Re: [RFC 2/2] x86, tsc: Enable clock for ealry printk timestamp
Date: Wed, 30 May 2018 22:17:29 +0800 [thread overview]
Message-ID: <20180530141729.5xulqmhjibynbm5d@shbuild888> (raw)
In-Reply-To: <CAHp75Vcii2=TDxBWeOve05peyiYiPeMu_ocBvj5SJ8UB+94eNQ@mail.gmail.com>
Hi Andy,
Thanks for the review.
On Wed, May 30, 2018 at 04:25:07PM +0300, Andy Shevchenko wrote:
> On Wed, May 30, 2018 at 12:20 PM, Feng Tang <feng.tang@intel.com> wrote:
> > To show time info in kernel log earlier and help optimizing kernel
> > boot time, printk adds a debug hook "boot_printk_clock_fn()" for
> > capable platform which has accurate clock in early boot phase.
> >
> > This patch will add early param setup option, so that user can
> > chose to provide a tsc based early printk clock simply by adding
> > in command line: "boot_tsc=xxxxM" (xxxxM is the stable TSC freq).
>
> > +
>
> This line is not needed.
Ok, will remove it.
>
> > + cur_tsc = rdtsc();
> > + cur_tsc -= boot_tsc_offset;
>
> In one expression?
Agree
>
> > + if (!p)
> > + return -EINVAL;
> > +
>
> I'm not sure it's needed at all.
>
> > + boot_tsc_mhz = div64_u64(tsc_hz, 1024 * 1024);
>
> Hmm... 1024*1024 != 1000 * 1000. So, hz -> mhz here (as by suffixes)
> looks weird.
The memparse is mostly for memory stuff which takes 1M as 1024*1024,
but for TSC frequency 1M means 1000*1000, and the code is trying to
do some awkward translation.
But you are right, this code will break if user doesn't use expression
with 'm".
>
> > + if (boot_tsc_mhz == 0)
> > + return -EINVAL;
>
> > + pr_info("TSC has run for %lld us\n",
> > + div64_u64(boot_tsc_offset, boot_tsc_mhz));
> > +
> > + /* Setup the early printk clock */
> > + boot_printk_clock_fn = boot_tsc_clock;
>
> > + pr_info("TSC: Setup early printk timestamp with %lldM TSC.",
> > + boot_tsc_mhz);
>
> Perhaps remove period (above doesn't have it) and move this to one line?
You mean merge the two pr_info line? yes, we can do that.
Thanks,
Feng
next prev parent reply other threads:[~2018-05-30 14:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 9:20 [RFC 1/2] printk: Enable platform to provide a early boot clock Feng Tang
2018-05-30 9:20 ` [RFC 2/2] x86, tsc: Enable clock for ealry printk timestamp Feng Tang
2018-05-30 13:25 ` Andy Shevchenko
2018-05-30 14:17 ` Feng Tang [this message]
2018-05-31 13:55 ` Petr Mladek
2018-05-31 15:52 ` Peter Zijlstra
2018-06-01 16:12 ` Feng Tang
2018-06-06 9:38 ` Feng Tang
2018-06-06 15:25 ` Pavel Tatashin
2018-06-07 1:34 ` Feng Tang
2018-06-13 7:29 ` Feng Tang
2018-06-01 18:05 ` Pavel Tatashin
2018-05-31 7:18 ` [RFC 1/2] printk: Enable platform to provide a early boot clock Andy Shevchenko
2018-05-31 17:22 ` Randy Dunlap
2018-05-31 18:15 ` Andy Shevchenko
2018-06-14 8:38 ` Feng Tang
2018-06-14 9:08 ` Thomas Gleixner
2018-06-14 9:55 ` Feng Tang
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=20180530141729.5xulqmhjibynbm5d@shbuild888 \
--to=feng.tang@intel.com \
--cc=alek.du@intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
/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®