From: Feng Tang <feng.tang@intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Clemens Ladisch <clemens@ladisch.de>,
tglx@linutronix.de, mingo@elte.hu, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: hpet: Don't default CONFIG_HPET_TIMER to be y for X86_64
Date: Fri, 28 Mar 2014 10:48:13 +0800 [thread overview]
Message-ID: <20140328024813.GB31111@feng-snb> (raw)
In-Reply-To: <53348199.7070207@mit.edu>
On Thu, Mar 27, 2014 at 12:52:57PM -0700, Andy Lutomirski wrote:
> On 03/27/2014 04:02 AM, Clemens Ladisch wrote:
> > Feng Tang wrote:
> >> On many new phone/tablet platforms like Baytrail/Merrifield etc,
> >> the HPET are either defeatured or has some problem to be used
> >> as a reliable timer. As these platforms also have X86_64, we
> >> should not make HPET_TIMER default y for all X86_64.
>
> Wouldn't it be better to fix the hpet driver so that the hpet doesn't
> used on these platforms?
>
> >
> > The help text still says:
> > | You can safely choose Y here. [...]
> > | Choose N to continue using the legacy 8254 timer.
> >
> > Are these statements still true for those platforms?
>
> They aren't true for modern desktop and server platforms -- the TSC is
> used regardless of hpet availability.
The way of using TSC varies depends on the generations of platforms.
Thomas Gleixner once gave a very good description, which link I personally
bookmarked, and would share here:
https://lkml.org/lkml/2013/5/8/202
Thanks,
Feng
prev parent reply other threads:[~2014-03-28 2:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 7:45 [PATCH] x86: hpet: Don't default CONFIG_HPET_TIMER to be y for X86_64 Feng Tang
2014-03-27 11:02 ` Clemens Ladisch
2014-03-27 19:52 ` Andy Lutomirski
2014-03-27 21:27 ` John Stultz
2014-03-27 21:33 ` Andy Lutomirski
2014-03-27 21:52 ` John Stultz
2014-03-28 2:43 ` Feng Tang
2014-03-28 2:48 ` Feng Tang [this message]
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=20140328024813.GB31111@feng-snb \
--to=feng.tang@intel.com \
--cc=clemens@ladisch.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@elte.hu \
--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