mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: John Stultz <john.stultz@linaro.org>
Cc: Jeff Merkey <linux.mdb@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG REPORT] ktime_get_ts64 causes Hard Lockup
Date: Wed, 20 Jan 2016 18:42:23 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.11.1601201837300.3575@nanos> (raw)
In-Reply-To: <CALAqxLXMUcucGd7xQ8JD120LdiOr9qbb-RybwJYx95c=V+9p7w@mail.gmail.com>

On Wed, 20 Jan 2016, John Stultz wrote:
> Ehrm.  A more productive route in solving this might be to cap the
> cycle delta we return from timekeeping_get_delta().
> 
> We already do this in the CONFIG_DEBUG_TIMEKEEPING, but adding a
> simple check it to the non-debug case should be doable w/o adding too
> much overhead to this very hot path.
> 
> Something like:
> if (delta > tkr->clock->max_cycles)
>     delta = tkr->clock->max_cycles;
> 
> return delta;

Well, you can make CONFIG_KDB select CONFIG_DEBUG_TIMEKEEPING.

Thanks,

	tglx

  parent reply	other threads:[~2016-01-20 17:43 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-19  1:59 Jeff Merkey
2016-01-19  2:16 ` Jeff Merkey
2016-01-19  2:31   ` Jeff Merkey
2016-01-19  9:50 ` Thomas Gleixner
2016-01-19 15:37 ` Jeff Merkey
2016-01-19 22:00   ` Jeff Merkey
2016-01-20  0:59     ` Jeff Merkey
2016-01-20  9:21     ` Thomas Gleixner
2016-01-20 14:26       ` Thomas Gleixner
2016-01-20 16:40         ` Jeff Merkey
2016-01-20 16:53       ` Jeff Merkey
2016-01-20 17:16         ` Jeff Merkey
2016-01-20 17:32           ` John Stultz
2016-01-20 17:36             ` Jeff Merkey
2016-01-20 17:42             ` Thomas Gleixner [this message]
2016-01-20 17:59               ` John Stultz
2016-01-20 18:03                 ` Jeff Merkey
2016-01-20 17:21         ` Thomas Gleixner
2016-01-20 17:33           ` Jeff Merkey
2016-01-20 19:34             ` Thomas Gleixner
2016-01-20 19:59               ` Jeff Merkey
2016-01-21  7:09                 ` Jeff Merkey
2016-01-21  8:18                   ` Jeff Merkey
2016-01-21  9:08                     ` Jeff Merkey
2016-01-21 10:12                   ` Thomas Gleixner
2016-01-21 15:46                     ` Jeff Merkey
2016-01-21 16:57                       ` Jeff Merkey
2016-01-21 17:00                         ` Jeff Merkey
2016-01-21 17:07                           ` Jeff Merkey

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.11.1601201837300.3575@nanos \
    --to=tglx@linutronix.de \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux.mdb@gmail.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 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®