From: Frederic Weisbecker <frederic@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <frederic@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Eric W . Biederman" <ebiederm@xmission.com>,
Oleg Nesterov <oleg@redhat.com>, Ingo Molnar <mingo@kernel.org>
Subject: [PATCH 0/6] posix-cpu-timers: Bunch of fixes
Date: Fri, 4 Jun 2021 13:31:53 +0200 [thread overview]
Message-ID: <20210604113159.26177-1-frederic@kernel.org> (raw)
The first is a race due to locklessly starting process wide cputime
counting.
The others stop the process wide cputime counting and tick dependency
when they are not necessary anymore.
Note I don't really like patch 5/6 and in fact I hope we could manage to
remove this early inline cpu_timer_fire() call from timer_settime(). All
we get from it is headaches. Besides, the handler isn't invoked from the
actual target and that doesn't sound ideal.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
timers/urgent
HEAD: f8f908c9d2b2f1e100cd549206c95a4e65e5f023
Thanks,
Frederic
---
Frederic Weisbecker (6):
posix-cpu-timers: Fix rearm racing against process tick
posix-cpu-timers: Don't start process wide cputime counter if timer is disabled
posix-cpu-timers: Force next_expiration recalc after timer deletion
posix-cpu-timers: Force next_expiration recalc after timer reset
posix-cpu-timers: Force next expiration recalc after early timer firing
posix-cpu-timers: Force next expiration recalc after itimer reset
include/linux/posix-timers.h | 11 ++++-
kernel/time/posix-cpu-timers.c | 97 +++++++++++++++++++++++++++++++++---------
2 files changed, 87 insertions(+), 21 deletions(-)
next reply other threads:[~2021-06-04 11:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 11:31 Frederic Weisbecker [this message]
2021-06-04 11:31 ` [PATCH 1/6] posix-cpu-timers: Fix rearm racing against process tick Frederic Weisbecker
2021-06-09 11:54 ` Frederic Weisbecker
2021-06-11 11:49 ` Peter Zijlstra
2021-06-11 12:37 ` Frederic Weisbecker
2021-06-04 11:31 ` [PATCH 2/6] posix-cpu-timers: Don't start process wide cputime counter if timer is disabled Frederic Weisbecker
2021-06-09 12:18 ` Frederic Weisbecker
2021-06-10 10:24 ` Frederic Weisbecker
2021-06-16 8:51 ` Peter Zijlstra
2021-06-16 10:51 ` Frederic Weisbecker
2021-06-16 11:26 ` Peter Zijlstra
2021-06-16 11:50 ` Peter Zijlstra
2021-06-04 11:31 ` [PATCH 3/6] posix-cpu-timers: Force next_expiration recalc after timer deletion Frederic Weisbecker
2021-06-16 9:16 ` Peter Zijlstra
2021-06-04 11:31 ` [PATCH 4/6] posix-cpu-timers: Force next_expiration recalc after timer reset Frederic Weisbecker
2021-06-16 9:23 ` Peter Zijlstra
2021-06-16 11:21 ` Frederic Weisbecker
2021-06-16 11:33 ` Peter Zijlstra
2021-06-04 11:31 ` [PATCH 5/6] posix-cpu-timers: Force next expiration recalc after early timer firing Frederic Weisbecker
2021-06-16 9:42 ` Peter Zijlstra
2021-06-16 11:59 ` Frederic Weisbecker
2021-06-16 13:23 ` Peter Zijlstra
2021-06-16 14:53 ` Frederic Weisbecker
2021-06-04 11:31 ` [PATCH 6/6] posix-cpu-timers: Force next expiration recalc after itimer reset 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=20210604113159.26177-1-frederic@kernel.org \
--to=frederic@kernel.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.