From: Mike Travis <mike.travis@hpe.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: Hedi Berriche <hedi@sgi.com>,
Russ Anderson <russ.anderson@hpe.com>,
Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Borislav Petkov <bp@alien8.de>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philippe Ombredanne <pombredanne@nexb.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Dave Hansen <dave.hansen@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ram Pai <linuxram@us.ibm.com>, Juergen Gross <jgross@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>, Petr Tesarik <ptesarik@suse.cz>,
Sinan Kaya <okaya@codeaurora.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Fix community TSC ADJUST breakage causing TSC failure
Date: Mon, 01 Oct 2018 20:22:04 -0500 [thread overview]
Message-ID: <20181002012204.297193336@stormcage.americas.sgi.com> (raw)
Fix a breakage caused by enabling early tsc initialization which bypasses
a check that disables the forcing of TSC ADJUST to 0 for chassis 0.
This is common on systems where all the chassis start up asynchronously
so which chassis should have a TSC ADJUST value of 0 is not predictable.
The solution is to add a check earlier than this early tsc init to
disable the potential of it incorrectly adjusting TSC ADJUST values that
are already correctly initialized.
* Patch 1 adds an early callable function (right after efi_init) that
will check if this system might be a UV system.
* Patch 2 adds code into setup_arch() which disables the call to
tsc_early_init. This function calls the TSC adjust initialization
functions before UV setup has checked if BIOS has set the multi-chassis
sync flags. Further references are in the patch.
--
next reply other threads:[~2018-10-02 1:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 1:22 Mike Travis [this message]
2018-10-02 1:22 ` [PATCH 1/2] x86/platform/uv: Add is_early_uv_system check Mike Travis
2018-10-02 6:20 ` Thomas Gleixner
2018-10-02 14:20 ` Mike Travis
2018-10-02 14:23 ` Thomas Gleixner
2018-10-02 1:22 ` [PATCH 2/2] x86/tsc: Fix UV TSC initialization Mike Travis
2018-10-02 6:22 ` Thomas Gleixner
2018-10-02 14:21 ` Mike Travis
2018-10-02 6:24 ` [PATCH 0/2] Fix community TSC ADJUST breakage causing TSC failure Thomas Gleixner
2018-10-02 14:26 ` Travis, Mike
2018-10-02 14:28 ` Thomas Gleixner
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=20181002012204.297193336@stormcage.americas.sgi.com \
--to=mike.travis@hpe.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dimitri.sivanich@hpe.com \
--cc=gregkh@linuxfoundation.org \
--cc=hedi@sgi.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mingo@redhat.com \
--cc=okaya@codeaurora.org \
--cc=pasha.tatashin@oracle.com \
--cc=pombredanne@nexb.com \
--cc=ptesarik@suse.cz \
--cc=russ.anderson@hpe.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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 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.