Hi,
The changes since v1 (https://lkml.org/lkml/2012/7/27/286) are:
- change naming from "user hooks" to "code domain tracking".
- use of __this_cpu_* APIs instead of __get_cpu_*
There is still a dependency against Paul's rcu/idle branch
and the vtime consolidation set:
Hi,
The changes since v1 (https://lkml.org/lkml/2012/7/27/286) are:
- change naming from user hooks to code domain tracking.
- use of __this_cpu_* APIs instead of __get_cpu_*
There is still a dependency against Paul's rcu/idle branch
and the vtime consolidation set:
So,
This is a proposition to handle the cputime accounting without the
tick to prepare for stopping the tick further idle.
I have managed to reuse and generalize the kernel/user boundary
hooks used by RCU. This way we can minimize the changes in archs
that don't support virtual cputime and we
So,
This is a proposition to handle the cputime accounting without the
tick to prepare for stopping the tick further idle.
I have managed to reuse and generalize the kernel/user boundary
hooks used by RCU. This way we can minimize the changes in archs
that don't support virtual cputime and we
4 matches
Mail list logo
