From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-kernel@vger.kernel.org
Cc: Fernando Luis Vazquez Cao <fernando_b1@lab.ntt.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@linux.intel.com>,
Oleg Nesterov <oleg@redhat.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: [PATCH 0/2 v2] nohz: fix idle accounting in NO_HZ kernels
Date: Mon, 31 Mar 2014 11:01:42 +0900 [thread overview]
Message-ID: <5338CC86.9080602@jp.fujitsu.com> (raw)
Hi all,
This patch set (rebased on v3.14-rc8) will fix an issue that
idle/iowait of /proc/stat can go backward. Originally reported
by Tetsuo and Fernando at last year, Mar 2013.
v2 have Preeti's Reviewed-by (Thanks!).
Of course still reviews are welcome.
Thanks,
H.Seto
Hidetoshi Seto (2):
nohz: use seqlock to avoid race on idle time stats v2
nohz, procfs: introduce get_cpu_idle/iowait_time_coarse
fs/proc/stat.c | 16 ++---
include/linux/tick.h | 5 +
kernel/time/tick-sched.c | 197 ++++++++++++++++++++++++++++++++++++++++------
3 files changed, 183 insertions(+), 35 deletions(-)
next reply other threads:[~2014-03-31 2:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 2:01 Hidetoshi Seto [this message]
2014-03-31 2:08 ` [PATCH 1/2] nohz: use seqlock to avoid race on idle time stats v2 Hidetoshi Seto
2014-04-02 19:35 ` Denys Vlasenko
2014-04-03 7:02 ` Hidetoshi Seto
2014-04-03 9:51 ` Denys Vlasenko
2014-04-04 2:47 ` Hidetoshi Seto
2014-04-04 16:03 ` Frederic Weisbecker
2014-04-04 17:02 ` Denys Vlasenko
2014-04-05 10:08 ` Frederic Weisbecker
2014-04-05 14:56 ` Denys Vlasenko
2014-04-07 18:17 ` Frederic Weisbecker
2014-04-09 12:49 ` Denys Vlasenko
2014-04-09 13:42 ` Peter Zijlstra
2014-03-31 2:09 ` [PATCH 2/2] nohz, procfs: introduce get_cpu_idle/iowait_time_coarse Hidetoshi Seto
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=5338CC86.9080602@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=fernando_b1@lab.ntt.co.jp \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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