From: Mike Travis <mike.travis@hpe.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Bin Gao <bin.gao@linux.intel.com>,
Prarit Bhargava <prarit@redhat.com>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Andrew Banman <andrew.banman@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 4/5] x86/kernel: Provide a means to disable TSC ART
Date: Wed, 4 Oct 2017 07:15:17 -0700 [thread overview]
Message-ID: <d37dffa7-c69e-72ed-b777-e7fe742ed5b4@hpe.com> (raw)
In-Reply-To: <20171004092704.mm4q5ivrlfrcj6sk@hirez.programming.kicks-ass.net>
On 10/4/2017 2:27 AM, Peter Zijlstra wrote:
> On Mon, Oct 02, 2017 at 10:12:18AM -0500, mike.travis@hpe.com wrote:
>> static void detect_art(void)
>> {
>> unsigned int unused[2];
>>
>> - if (boot_cpu_data.cpuid_level < ART_CPUID_LEAF)
>> + if (boot_cpu_data.cpuid_level < ART_CPUID_LEAF || tsc_art_disabled)
>> return;
>>
>> /* Don't enable ART in a VM, non-stop TSC and TSC_ADJUST required */
>
>
> So why can't we use is_uv_system() here an for the tsc_adjust thing?
I could. I just thought that there may be future system arches that
need the same facility?
>
> Also (and I hate the name) tsc_multi_sync_resets is the reason you
> cannot use ART, I don't think it makes sense to introduce yet another
> knob.
>
Okay. I wasn't sure if there might be different causes for wanting one
condition over the other. So does this mean change this later test to
use is_uv_system() or tsc_multi_sync_resets?
Thanks.
next prev parent reply other threads:[~2017-10-04 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 15:12 [PATCH 0/5] x86/platform/UV: Update TSC support mike.travis
2017-10-02 15:12 ` [PATCH 1/5] x86/kernel: Add option that TSC on Socket 0 being non-zero is valid mike.travis
2017-10-02 15:12 ` [PATCH 2/5] x86/kernel: Skip TSC test and error messages if already unstable mike.travis
2017-10-02 15:12 ` [PATCH 3/5] x86/kernel: Drastically reduce the number of firmware bug warnings mike.travis
2017-10-02 15:12 ` [PATCH 4/5] x86/kernel: Provide a means to disable TSC ART mike.travis
2017-10-04 9:27 ` Peter Zijlstra
2017-10-04 14:15 ` Mike Travis [this message]
2017-10-04 18:50 ` Thomas Gleixner
2017-10-02 15:12 ` [PATCH 5/5] x86/platform/UV: Add check of TSC state set by UV BIOS mike.travis
2017-10-05 16:47 [PATCH 0/5] x86/platform/UV: Update TSC support mike.travis
2017-10-05 16:47 ` [PATCH 4/5] x86/kernel: Provide a means to disable TSC ART mike.travis
2017-10-12 16:32 [PATCH 0/5] x86/platform/UV: Update TSC support mike.travis
2017-10-12 16:32 ` [PATCH 4/5] x86/kernel: Provide a means to disable TSC ART mike.travis
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=d37dffa7-c69e-72ed-b777-e7fe742ed5b4@hpe.com \
--to=mike.travis@hpe.com \
--cc=andrew.banman@hpe.com \
--cc=bin.gao@linux.intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=prarit@redhat.com \
--cc=russ.anderson@hpe.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
all inboxes | Powered by JetHome®