Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

2017-07-15 11:37 GMT+08:00 Levin, Alexander (Sasha Levin) : > On Thu, Jun 29, 2017 at 07:15:11PM +0200, Frederic Weisbecker wrote: >>From: Wanpeng Li >> >>Currently the cputime source used by vtime is jiffies. When we cross >>a context boundary

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

2017-07-15 11:37 GMT+08:00 Levin, Alexander (Sasha Levin) : > On Thu, Jun 29, 2017 at 07:15:11PM +0200, Frederic Weisbecker wrote: >>From: Wanpeng Li >> >>Currently the cputime source used by vtime is jiffies. When we cross >>a context boundary and jiffies have changed since the last snapshot,

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, Jun 29, 2017 at 07:15:11PM +0200, Frederic Weisbecker wrote: >From: Wanpeng Li > >Currently the cputime source used by vtime is jiffies. When we cross >a context boundary and jiffies have changed since the last snapshot, the >pending cputime is accounted to the

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, Jun 29, 2017 at 07:15:11PM +0200, Frederic Weisbecker wrote: >From: Wanpeng Li > >Currently the cputime source used by vtime is jiffies. When we cross >a context boundary and jiffies have changed since the last snapshot, the >pending cputime is accounted to the switching out context. >

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, Jun 29, 2017 at 07:27:27PM -0400, Rik van Riel wrote: > On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > > From: Wanpeng Li > > > > Currently the cputime source used by vtime is jiffies. When we cross > > a context boundary and jiffies have changed

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, Jun 29, 2017 at 07:27:27PM -0400, Rik van Riel wrote: > On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > > From: Wanpeng Li > > > > Currently the cputime source used by vtime is jiffies. When we cross > > a context boundary and jiffies have changed since the last snapshot,

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

2017-06-30 1:15 GMT+08:00 Frederic Weisbecker : > From: Wanpeng Li From: Wanpeng Li > > Currently the cputime source used by vtime is jiffies. When we cross > a context boundary and jiffies have changed since the last snapshot,

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

2017-06-30 1:15 GMT+08:00 Frederic Weisbecker : > From: Wanpeng Li From: Wanpeng Li > > Currently the cputime source used by vtime is jiffies. When we cross > a context boundary and jiffies have changed since the last snapshot, the > pending cputime is accounted to the switching out context. >

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > From: Wanpeng Li > > Currently the cputime source used by vtime is jiffies. When we cross > a context boundary and jiffies have changed since the last snapshot, > the > pending cputime is accounted to the

Re: [PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > From: Wanpeng Li > > Currently the cputime source used by vtime is jiffies. When we cross > a context boundary and jiffies have changed since the last snapshot, > the > pending cputime is accounted to the switching out context. > >

[PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

From: Wanpeng Li Currently the cputime source used by vtime is jiffies. When we cross a context boundary and jiffies have changed since the last snapshot, the pending cputime is accounted to the switching out context. This system works ok if the ticks are not aligned across

[PATCH 5/5] sched: Accumulate vtime on top of nsec clocksource

From: Wanpeng Li Currently the cputime source used by vtime is jiffies. When we cross a context boundary and jiffies have changed since the last snapshot, the pending cputime is accounted to the switching out context. This system works ok if the ticks are not aligned across CPUs. If they