From: Thomas Gleixner <tglx@linutronix.de>
To: Mike Travis <mike.travis@hpe.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
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: Re: [PATCH 0/2] Fix community TSC ADJUST breakage causing TSC failure
Date: Tue, 2 Oct 2018 08:24:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1810020823550.32062@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20181002012204.297193336@stormcage.americas.sgi.com>
On Mon, 1 Oct 2018, Mike Travis wrote:
I'm not sure what a 'community TSC adjust breakage' means.
next prev parent reply other threads:[~2018-10-02 6:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 1:22 [PATCH 0/2] Fix community TSC ADJUST breakage causing TSC failure Mike Travis
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 ` Thomas Gleixner [this message]
2018-10-02 14:26 ` [PATCH 0/2] Fix community TSC ADJUST breakage causing TSC failure 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=alpine.DEB.2.21.1810020823550.32062@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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=mike.travis@hpe.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=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.