From: Lu Baolu <baolu.lu@linux.intel.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Ingo Molnar <mingo@redhat.com>
Cc: Mathias Nyman <mathias.nyman@linux.intel.com>,
tglx@linutronix.de, peterz@infradead.org,
linux-usb@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/5] x86: add simple udelay calibration
Date: Wed, 15 Feb 2017 10:33:39 +0800 [thread overview]
Message-ID: <58A3BE03.2010805@linux.intel.com> (raw)
In-Reply-To: <b7126beb-0956-b589-9d82-163f8e3645fb@cogentembedded.com>
Hi,
On 02/14/2017 05:23 PM, Sergei Shtylyov wrote:
> Hello!
>
> On 2/14/2017 5:27 AM, Lu Baolu wrote:
>
>> Add a simple udelay calibration in x86 architecture-specific
>> boot-time initializations. This will get a workable estimate
>> for loops_per_jiffy. Hence, udelay() could be used after this
>> initialization.
>>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: x86@kernel.org
>> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com>
>> ---
>> arch/x86/kernel/setup.c | 22 ++++++++++++++++++++++
>> 1 file changed, 22 insertions(+)
>>
>> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
>> index 4cfba94..aab7faa 100644
>> --- a/arch/x86/kernel/setup.c
>> +++ b/arch/x86/kernel/setup.c
>> @@ -835,6 +835,26 @@ dump_kernel_offset(struct notifier_block *self, unsigned long v, void *p)
>> return 0;
>> }
>>
>> +static void __init simple_udelay_calibration(void)
>> +{
>> + unsigned int tsc_khz, cpu_khz;
>> + unsigned long lpj;
>> +
>> + if (!boot_cpu_has(X86_FEATURE_TSC))
>> + return;
>> +
>> + cpu_khz = x86_platform.calibrate_cpu();
>> + tsc_khz = x86_platform.calibrate_tsc();
>> +
>> + tsc_khz = tsc_khz ? : cpu_khz;
>
> Why not:
>
> if (!tsc_khz)
> tsc_khz = cpu_khz;
>
> It's more clear IMHO.
Sure.
Best regards,
Lu Baolu
>
>> + if (!tsc_khz)
>> + return;
>> +
>> + lpj = tsc_khz * 1000;
>> + do_div(lpj, HZ);
>> + loops_per_jiffy = lpj;
>> +}
>> +
>> /*
>> * Determine if we were loaded by an EFI loader. If so, then we have also been
>> * passed the efi memmap, systab, etc., so we should use these data structures
> [...]
>
> MBR, Sergei
>
>
next prev parent reply other threads:[~2017-02-15 2:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 2:27 [PATCH v7 0/5] usb: early: add support for early printk through USB3 debug port Lu Baolu
2017-02-14 2:27 ` [PATCH v7 1/5] x86: add simple udelay calibration Lu Baolu
2017-02-14 9:23 ` Sergei Shtylyov
2017-02-15 2:33 ` Lu Baolu [this message]
2017-02-14 2:27 ` [PATCH v7 2/5] usb: dbc: early driver for xhci debug capability Lu Baolu
2017-02-14 2:27 ` [PATCH v7 3/5] x86: add support for earlyprintk via USB3 debug port Lu Baolu
2017-02-14 2:27 ` [PATCH v7 4/5] usb: serial: add dbc debug device support to usb_debug Lu Baolu
2017-02-14 2:27 ` [PATCH v7 5/5] usb: doc: add document for USB3 debug port usage Lu Baolu
[not found] ` <CAL411-o5xaA+awYi9zEZog1zCZvMCvNQ0i0R7yh24_zrTuu4gQ@mail.gmail.com>
2017-02-14 4:41 ` Lu Baolu
2017-02-14 6:13 ` Peter Chen
2017-02-14 7:20 ` Lu Baolu
2017-03-02 2:17 ` [PATCH v7 0/5] usb: early: add support for early printk through USB3 debug port Lu Baolu
2017-03-02 6:40 ` Ingo Molnar
2017-03-03 8:22 ` Lu Baolu
2017-03-16 7:17 ` Ingo Molnar
2017-03-17 2:37 ` Lu Baolu
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=58A3BE03.2010805@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sergei.shtylyov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).