From: Ingo Molnar <mingo@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
Kosaki Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL v2] posix cpu timers cleanups for 3.14
Date: Tue, 10 Dec 2013 12:34:16 +0100 [thread overview]
Message-ID: <20131210113416.GC26659@gmail.com> (raw)
In-Reply-To: <1386613447-5042-1-git-send-email-fweisbec@gmail.com>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> Ingo, Thomas,
>
> Please pull the timers/posix-timers-for-tip-v2 branch that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
> timers/posix-timers-for-tip-v2
>
> HEAD: 531f64fd6f46a3f2a3edb1b97ecc827c775932c5
>
> This is the second version of the pull request that I sent you a few weeks ago:
> http://lkml.kernel.org/r/1385221040-24731-1-git-send-email-fweisbec@gmail.com
>
> Changes in this v2:
>
> * rebase against latest tip:timers/core (there was a conflict with some dynticks
> patches)
>
> * add a cleanup suggested by Kosaki in patch 02/10: remove a useless group
> timer sample snapshot and rearm on timer rescheduling.
>
> Also the previous pull request lacked a high level overall description, so I'm
> adding one here.
>
> ---
>
> Posix cpu timers changes for 3.14:
>
> * Remove dying thread/process timers caching that were complicating the code
> for no significant win.
>
> * Remove early task reference release on dying timer sample read. Again it was
> not worth the code complication. The other timer's resources aren't released until
> timer_delete() is called anyway (or when the whole process dies).
>
> * Remove leftover arguments in reaped target cleanup
>
> * Consolidate some timer sampling code
>
> * Remove use of tasklist lock
>
> * Robustify sighand locking against exec and exit by using the safer
> lock_task_sighand() API instead of sighand raw locking.
>
> * Convert some unnecessary BUG_ON() to WARN_ON()
>
>
> Thanks,
> Frederic
> ---
>
> Frederic Weisbecker (10):
> posix-timers: Remove dead thread posix cpu timers caching
> posix-timers: Remove dead process posix cpu timers caching
> posix-timers: Cleanup reaped target handling
> posix-timers: Remove dead task special case
> posix-timers: Remove useless clock sample on timers cleanup
> posix-timers: Consolidate posix_cpu_clock_get()
> posix-timers: Use sighand lock instead of tasklist_lock for task clock sample
> posix-timers: Use sighand lock instead of tasklist_lock on timer deletion
> posix-timers: Remove remaining uses of tasklist_lock
> posix-timers: Convert abuses of BUG_ON to WARN_ON
>
>
> kernel/posix-cpu-timers.c | 312 +++++++++++++++++++---------------------------
> 1 file changed, 129 insertions(+), 183 deletions(-)
Pulled, thanks a lot Frederic!
Ingo
prev parent reply other threads:[~2013-12-10 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 18:24 [GIT PULL v2] posix cpu timers cleanups for 3.14 Frederic Weisbecker
2013-12-10 11:34 ` Ingo Molnar [this message]
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=20131210113416.GC26659@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox