mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kosaki.motohiro@gmail.com
To: linux-kernel@vger.kernel.org
Cc: Olivier Langlois <olivier@trillion01.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: [PATCH v4 0/7] posix timers fixlet
Date: Fri,  3 May 2013 00:47:40 -0400	[thread overview]
Message-ID: <1367556468-4021-1-git-send-email-kosaki.motohiro@gmail.com> (raw)

From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>

Glibc's posix timer testcase found a lot of bugs in posix timer code.
This series, hopefully, fixes all of them. All patches are independent 
each other logically.

Changes from v3
 - task_sched_runtime() micro optimization add to care tsk->on_cpu.
   suggested Paul Turner.
 - fixed several typo in changelogs.


KOSAKI Motohiro (7):
  posix-cpu-timers: don't account cpu timer after stopped thread
    runtime accounting
  posix-cpu-timers: fix acounting delta_exec twice
  posix-cpu-timers: fix wrong timer initialization
  posix-cpu-timers: timer functions should use timer time instead of
    clock time
  posix-cpu-timers: check_thread_timers() uses task_sched_runtime()
  sched: task_sched_runtime introduce micro optimization
  posix-cpu-timers: cleanup cpu_{clock,timer}_sample{,_group}

 fs/binfmt_elf.c             |    2 +-
 fs/binfmt_elf_fdpic.c       |    2 +-
 include/linux/kernel_stat.h |    5 --
 include/linux/sched.h       |    5 +-
 kernel/posix-cpu-timers.c   |  143 ++++++++++++++++++++++++-------------------
 kernel/sched/core.c         |   34 ++++++-----
 kernel/sched/cputime.c      |   19 +++++-
 kernel/sched/stats.h        |    7 ++
 8 files changed, 125 insertions(+), 92 deletions(-)


             reply	other threads:[~2013-05-03  4:48 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  4:47 kosaki.motohiro [this message]
2013-05-03  4:47 ` [PATCH 1/7] posix-cpu-timers: don't account cpu timer after stopped thread runtime accounting kosaki.motohiro
2013-05-06 23:47   ` Frederic Weisbecker
2013-05-07  2:57     ` KOSAKI Motohiro
2013-05-07 15:24       ` Frederic Weisbecker
2013-05-26 21:38         ` KOSAKI Motohiro
2013-05-07  3:16     ` Olivier Langlois
2013-05-11  0:17       ` Frederic Weisbecker
2013-05-11  2:40         ` KOSAKI Motohiro
2013-05-03  4:47 ` [PATCH 2/7] posix-cpu-timers: fix acounting delta_exec twice kosaki.motohiro
2013-05-11  0:56   ` Frederic Weisbecker
2013-05-11  2:17     ` KOSAKI Motohiro
2013-05-03  4:47 ` [PATCH 3/7] posix-cpu-timers: fix wrong timer initialization kosaki.motohiro
2013-05-03  4:47 ` [PATCH 4/7] posix-cpu-timers: timer functions should use timer time instead of clock time kosaki.motohiro
2013-05-03  4:47 ` [PATCH 5/7] posix-cpu-timers: check_thread_timers() uses task_sched_runtime() kosaki.motohiro
2013-05-03  4:47 ` [PATCH 6/7] sched: task_sched_runtime introduce micro optimization kosaki.motohiro
2013-05-03  4:47 ` [PATCH 7/7] posix-cpu-timers: cleanup cpu_{clock,timer}_sample{,_group} kosaki.motohiro

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=1367556468-4021-1-git-send-email-kosaki.motohiro@gmail.com \
    --to=kosaki.motohiro@gmail.com \
    --cc=fweisbec@gmail.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=olivier@trillion01.com \
    --cc=peterz@infradead.org \
    --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

all inboxes | Powered by JetHome®