2012/12/31 Li Zhong :
> On Sat, 2012-12-29 at 17:42 +0100, Frederic Weisbecker wrote:
>> static inline void vtime_task_switch(struct task_struct *prev) { }
>> static inline void vtime_account_system(struct task_struct *tsk) { }
>> static inline void vtime_account_system_irqsafe(struct
2012/12/31 Li Zhong zh...@linux.vnet.ibm.com:
On Sat, 2012-12-29 at 17:42 +0100, Frederic Weisbecker wrote:
static inline void vtime_task_switch(struct task_struct *prev) { }
static inline void vtime_account_system(struct task_struct *tsk) { }
static inline void
On Sat, 2012-12-29 at 17:42 +0100, Frederic Weisbecker wrote:
> While remotely reading the cputime of a task running in a
> full dynticks CPU, the values stored in utime/stime fields
> of struct task_struct may be stale. Its values may be those
> of the last kernel <-> user transition time
On Sat, 2012-12-29 at 17:42 +0100, Frederic Weisbecker wrote:
While remotely reading the cputime of a task running in a
full dynticks CPU, the values stored in utime/stime fields
of struct task_struct may be stale. Its values may be those
of the last kernel - user transition time snapshot and
While remotely reading the cputime of a task running in a
full dynticks CPU, the values stored in utime/stime fields
of struct task_struct may be stale. Its values may be those
of the last kernel <-> user transition time snapshot and
we need to add the tickless time spent since this snapshot.
To
While remotely reading the cputime of a task running in a
full dynticks CPU, the values stored in utime/stime fields
of struct task_struct may be stale. Its values may be those
of the last kernel - user transition time snapshot and
we need to add the tickless time spent since this snapshot.
To
6 matches
Mail list logo
