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
Date: Thu, 20 Apr 2017 17:30:28 +0200 [thread overview]
Message-ID: <1492702230-28462-1-git-send-email-fweisbec@gmail.com> (raw)
Now that we've understood the issue that Pavel and Tim have reported,
here's the new version of 24b91e360ef521a2808771633d76ebc68bd5604b that
Linus reverted. I took extra care on CPU hotplug as well. Hopefully this
time the fix doesn't introduce a new bug. The second patch should warn
when such an issue arise.
Thanks.
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 | 28 ++++++++++++++++++++++++++--
kernel/time/tick-sched.h | 2 ++
2 files changed, 28 insertions(+), 2 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-20 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 15:30 Frederic Weisbecker [this message]
2017-04-20 15:30 ` [PATCH 1/2] nohz: Fix again collision between tick and other hrtimers Frederic Weisbecker
2017-04-20 16:00 ` Rik van Riel
2017-04-20 15:30 ` [PATCH 2/2] tick: Make sure tick timer is active when bypassing reprogramming Frederic Weisbecker
2017-04-20 16:01 ` Rik van Riel
2017-04-20 17:56 ` Thomas Gleixner
2017-04-20 18:29 ` Frederic Weisbecker
2017-04-20 19:40 ` Thomas Gleixner
2017-04-20 23:27 ` 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=1492702230-28462-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).