mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [GIT pull] x86/timers updates for 4.13
Date: Tue, 4 Jul 2017 09:27:12 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1707040925430.9000@nanos> (raw)
In-Reply-To: <CA+55aFyXwVqZbdgPf4gpA3ArxRpMyqKSxH40td=vUhLNh813fw@mail.gmail.com>

On Mon, 3 Jul 2017, Linus Torvalds wrote:
> On Mon, Jul 3, 2017 at 1:20 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > This update contains:
> >
> >    - The final solution for the TSC deadline timer borkage, which is caused
> >      by a hardware problem in the TSC_ADJUST/TSC_DEADLINE_TIMER logic.
> >
> >      The problem is documented now fixed with a microcode update, so we can
> >      remove the workaround and check for the microcode version. If the
> >      microcode is not up to date, then the TSC deadline timer is
> >      enabled. If the borkage is fixed by the proper micro code version,
> >      then the deadline timer can be used. In both cases the restrictions to
> >      the range of the TSC_ADJUST value, which were added as workarounds,
> >      are removed.
> >
> >   - A few simple fixes and updates to the timer related x86 code.
> 
> That deadline timer explanation made no sense.

Indeed. Sorry.

> I edited it to what I think you wanted to say in the commit message.

Yes. Thank you for fixing it up!

     tglx

      reply	other threads:[~2017-07-04  7:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03  8:20 Thomas Gleixner
2017-07-04  1:06 ` Linus Torvalds
2017-07-04  7:27   ` Thomas Gleixner [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=alpine.DEB.2.20.1707040925430.9000@nanos \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=torvalds@linux-foundation.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®