From: Frederic Weisbecker <fweisbec@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: [PATCH 0/2] nohz: Avoid double clock write
Date: Thu, 31 Jul 2014 18:45:54 +0200 [thread overview]
Message-ID: <1406825156-11901-1-git-send-email-fweisbec@gmail.com> (raw)
Hi Thomas,
The tick reschedules itself unconditionally. That's what we want as long
as the CPU is in periodic mode. It's not that relevant when the CPU
is in dynticks mode though as the clock write is likely to be overwritten
by the nohz code on irq exit.
In low-res mode, that even result in unexpected periodic behaviour when
no timer is scheduled in the future.
So here is a set that proposes the removal of these double writes.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
origin/nohz/drop-double-write-v2
Thanks,
Frederic
---
Viresh Kumar (2):
nohz: Fix spurious periodic tick behaviour in low-res dynticks mode
nohz: Avoid tick's double reprogramming in highres mode
kernel/time/tick-sched.c | 8 ++++++++
1 file changed, 8 insertions(+)
next reply other threads:[~2014-07-31 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 16:45 Frederic Weisbecker [this message]
2014-07-31 16:45 ` [PATCH 1/2] nohz: Fix spurious periodic tick behaviour in low-res dynticks mode Frederic Weisbecker
2014-07-31 16:45 ` [PATCH 2/2] nohz: Avoid tick's double reprogramming in highres mode Frederic Weisbecker
2014-08-11 23:00 ` [PATCH 0/2] nohz: Avoid double clock write 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=1406825156-11901-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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
Powered by JetHome