linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>,
	James Hartsock <hartsjc@redhat.com>,
	Tim Wright <tim@binbash.co.uk>, Pavel Machek <pavel@ucw.cz>
Subject: [PATCH 0/2] nohz: Deal with clock reprogram skipping issues v2
Date: Fri, 21 Apr 2017 16:00:53 +0200	[thread overview]
Message-ID: <1492783255-5051-1-git-send-email-fweisbec@gmail.com> (raw)

As suggested by Thomas Gleixner, the second patch now integrates
a fix in case the sanity check fails and the clockevent isn't programmed
as expected.

Frederic Weisbecker (2):
  nohz: Fix again collision between tick and other hrtimers
  tick: Make sure tick timer is active when bypassing reprogramming

 kernel/time/tick-sched.c | 33 ++++++++++++++++++++++++++++++---
 kernel/time/tick-sched.h |  2 ++
 2 files changed, 32 insertions(+), 3 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-21 14:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 14:00 Frederic Weisbecker [this message]
2017-04-21 14:00 ` [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers Frederic Weisbecker
2017-04-23 11:36   ` [tip:timers/urgent] " tip-bot for Frederic Weisbecker
2017-05-17  8:46   ` [tip:timers/nohz] nohz: Fix collision between tick and other hrtimers, again tip-bot for Frederic Weisbecker
2017-04-21 14:00 ` [PATCH 2/2] tick: Make sure tick timer is active when bypassing reprogramming Frederic Weisbecker
2017-04-23 11:37   ` [tip:timers/urgent] " tip-bot for Frederic Weisbecker
2017-06-03  8:06   ` [PATCH 2/2] " Levin, Alexander (Sasha Levin)
2017-06-03 12:42     ` Frederic Weisbecker
2017-06-03 13:00       ` Levin, Alexander (Sasha Levin)
2017-06-06 14:52         ` Frederic Weisbecker
2017-06-07  4:17           ` Levin, Alexander (Sasha Levin)
2017-06-07 14:14             ` Frederic Weisbecker
2017-06-07 21:36               ` Levin, Alexander (Sasha Levin)
2017-06-08 19:07                 ` [PATCH] nohz: Fix spurious warning when hrtimer and clockevent get out of sync Frederic Weisbecker
2017-06-08 22:13                   ` Levin, Alexander (Sasha Levin)
2017-06-09  0:48                     ` Frederic Weisbecker
2017-06-09 12:13                       ` Levin, Alexander (Sasha Levin)
2017-06-09 12:26                         ` Peter Zijlstra
2017-06-09 13:06                         ` Frederic Weisbecker
2017-04-24  8:08 ` [PATCH 0/2] nohz: Deal with clock reprogram skipping issues v2 Ingo Molnar
2017-04-24 14:04   ` Frederic Weisbecker
2017-04-24 14:45     ` Ingo Molnar
2017-04-26 14:55       ` Frederic Weisbecker
2017-04-26 18:49         ` Ingo Molnar
2017-04-26 21:07           ` Frederic Weisbecker
2017-04-24 17:01     ` [tip:timers/urgent] nohz: Print more debug info in tick_nohz_stop_sched_tick() tip-bot for Frederic Weisbecker

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=1492783255-5051-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=hartsjc@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=pavel@ucw.cz \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=tim@binbash.co.uk \
    /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;
as well as URLs for NNTP newsgroup(s).