From: Joe Korty <joe.korty@ccur.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Venki Pallipadi <venkatesh.pallipadi@intel.com>,
H Peter Anvin <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Support always running TSC on Intel CPUs
Date: Tue, 18 Nov 2008 09:55:40 -0500 [thread overview]
Message-ID: <20081118145540.GA32082@tsunami.ccur.com> (raw)
In-Reply-To: <20081118080952.GE17838@elte.hu>
On Tue, Nov 18, 2008 at 09:09:52AM +0100, Ingo Molnar wrote:
>
> * Venki Pallipadi <venkatesh.pallipadi@intel.com> wrote:
>
> > + if (c->x86_power & (1 << 8)) {
> > set_cpu_cap(c, X86_FEATURE_CONSTANT_TSC);
> > + set_cpu_cap(c, X86_FEATURE_NOSTOP_TSC);
> > + }
>
> hm, the naming is a bit confusing. We now have 3 variants:
>
> X86_FEATURE_TSC
> X86_FEATURE_CONSTANT_TSC
> X86_FEATURE_NOSTOP_TSC
>
> NOSTOP_TSC is basically what CONSTANT_TSC should have been to begin
> with ;-)
>
> i'd suggest to rename it to this:
>
> X86_FEATURE_TSC
> X86_FEATURE_CONSTANT_FREQ_TSC
> X86_FEATURE_STABLE_TSC
>
> ... with CONSTANT_FREQ_TSC not having any real role in the long run.
> (it's similarly problematic to a completely unstable TSC)
>
> does this sound ok?
To me, the new naming has the same head-scratching potential
as the old....
How about:
X86_FEATURE_TSC
X86_FEATURE_STABLE_TSC_OBSOLETE
X86_FEATURE_STABLE_TSC
Joe
next prev parent reply other threads:[~2008-11-18 15:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 0:11 [PATCH] x86: Support always running TSC on Intel CPUs Venki Pallipadi
2008-11-18 0:13 ` H. Peter Anvin
2008-11-18 0:16 ` Pallipadi, Venkatesh
2008-11-18 0:18 ` H. Peter Anvin
2008-11-18 0:49 ` Venki Pallipadi
2008-11-18 0:52 ` H. Peter Anvin
2008-11-18 1:05 ` Venki Pallipadi
2008-11-18 1:07 ` H. Peter Anvin
2008-11-18 3:26 ` Arjan van de Ven
2008-11-18 3:27 ` H. Peter Anvin
2008-11-18 8:09 ` Ingo Molnar
2008-11-18 14:55 ` Joe Korty [this message]
2008-11-18 16:05 ` Ingo Molnar
2008-11-18 16:47 ` Pallipadi, Venkatesh
2008-11-18 16:54 ` Joe Korty
2008-11-18 17:01 ` H. Peter Anvin
2008-11-18 16:48 ` Joe Korty
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=20081118145540.GA32082@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.