From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Stanislaw Gruszka <sgruszka@redhat.com>
Subject: [PATCH 0/4] Fix periodic itimers precision -v4
Date: Wed, 29 Jul 2009 12:15:25 +0200 [thread overview]
Message-ID: <1248862529-6063-1-git-send-email-sgruszka@redhat.com> (raw)
Hello,
I'm resending patches for fixing itimers periodic ticks precision,
for reference see: http://lkml.org/lkml/2009/4/2/230
Changelog:
v3 -> v4
- Rebase for 2.6.31
v2 -> v3 (resend 5):
- Use CPUCLOCK_PROF CPUCLOCK_VIRT defines in kernel/fork.c
- Using inline function cputime_sub_ns() with sanity check against negative
results instead of macro.
- Add patch which optimize jiffies_to_cputime(1) for PowerPC with
CONFIG_VIRT_CPU_ACCOUNTING
v1 -> v2 (resend 4):
- Add comment about CPUCLOCK_PROF and CPUCLOCK_VIRT are 0 and 1 respectively and
can be used for indexing itimers array.
- Remove not needed BUG().
- Coding style fixes.
- Better algorithm (idea form Thomas) to calculate next signal time for periodic
itimers, we use now precomputed nanosecond value of cputime 1 tick.
- Add patch with simplify arm_timer() function.
v0 -> v1 (resend 3):
- Fix bug: using utime instead of sum stime + utime when setup PROF itimer.
- Fix bug: using value->it_interval instead of ovalue->it_interavl.
- No new definitions IT_PROF and IT_VIRT only CPUCLOCK_PROF and CPUCLOCK_VIRT
are used.
Cheers
Stanislaw
next reply other threads:[~2009-07-29 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 10:15 Stanislaw Gruszka [this message]
2009-07-29 10:15 ` [PATCH 1/4] itimers: merge ITIMER_VIRT and ITIMER_PROF Stanislaw Gruszka
2009-07-29 10:15 ` [PATCH 2/4] itimers: fix periodic tics precision Stanislaw Gruszka
2009-07-29 10:15 ` [PATCH 3/4] itimers: simplify arm_timer() code a bit Stanislaw Gruszka
2009-07-29 10:15 ` [PATCH 4/4] cputime: optimize jiffies_to_cputime(1) Stanislaw Gruszka
2009-08-03 13:25 ` [tip:timers/posixtimers] cputime: Optimize jiffies_to_cputime(1) tip-bot for Stanislaw Gruszka
2009-08-03 13:25 ` [tip:timers/posixtimers] itimers: Simplify arm_timer() code a bit tip-bot for Stanislaw Gruszka
2009-08-03 13:24 ` [tip:timers/posixtimers] itimers: Fix periodic tics precision tip-bot for Stanislaw Gruszka
2009-08-03 13:24 ` [tip:timers/posixtimers] itimers: Merge ITIMER_VIRT and ITIMER_PROF tip-bot for Stanislaw Gruszka
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=1248862529-6063-1-git-send-email-sgruszka@redhat.com \
--to=sgruszka@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=paulus@samba.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