Re: [GIT PULL] cputime: Cleanups and optimizations

From: Ingo Molnar
Date: Tue Oct 30 2012 - 05:17:24 EST



* Frederic Weisbecker <fweisbec@xxxxxxxxx> wrote:

> Ingo,
>
> Please pull the latest cputime cleanups that can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git tags/cputime-cleanups-for-mingo
>
> for you to fetch changes up to 3e1df4f506836e6bea1ab61cf88c75c8b1840643:
>
> cputime: Separate irqtime accounting from generic vtime (2012-10-29 21:31:32 +0100)
>
> It is based on top of tip:sched/core of today.
>
> Tested on x86 and powerpc. Built-tested only on ia64 and s390.
>
> Thanks.
>
> ----------------------------------------------------------------
> Cputime cleanups and optimizations:
>
> * Gather vtime headers that were a bit scattered around
>
> * Separate irqtime and vtime namespaces that were
> colliding, resulting in useless calls to irqtime accounting.
>
> * Slightly optimize irq and guest vtime accounting.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@xxxxxxxxx>
>
> ----------------------------------------------------------------
> Frederic Weisbecker (5):
> vtime: Gather vtime declarations to their own header file
> vtime: Make vtime_account_system() irqsafe
> kvm: Directly account vtime to system on guest switch
> cputime: Specialize irq vtime hooks
> cputime: Separate irqtime accounting from generic vtime
>
> arch/ia64/kernel/time.c | 8 ++++----
> arch/powerpc/kernel/time.c | 4 ++--
> arch/s390/kernel/vtime.c | 4 ++++
> arch/s390/kvm/kvm-s390.c | 4 ----
> include/linux/hardirq.h | 15 +++-----------
> include/linux/kernel_stat.h | 9 +--------
> include/linux/kvm_host.h | 12 +++++++++--
> include/linux/vtime.h | 47 +++++++++++++++++++++++++++++++++++++++++++
> kernel/sched/cputime.c | 20 +++++++++++++-----
> kernel/softirq.c | 6 +++---
> 10 files changed, 89 insertions(+), 40 deletions(-)
> create mode 100644 include/linux/vtime.h

Pulled, thanks Frederic!

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/