Re: [PATCH 2/5] sched: Always set vtime_snap_whence after accounting vtime

2017-06-29 Thread Rik van Riel
On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > Even though it doesn't have functional consequences, setting > the task's new context state after we actually accounted the pending > vtime from the old context state makes more sense from a review > perspective. > >

Re: [PATCH 2/5] sched: Always set vtime_snap_whence after accounting vtime

2017-06-29 Thread Rik van Riel
On Thu, 2017-06-29 at 19:15 +0200, Frederic Weisbecker wrote: > Even though it doesn't have functional consequences, setting > the task's new context state after we actually accounted the pending > vtime from the old context state makes more sense from a review > perspective. > >

[PATCH 2/5] sched: Always set vtime_snap_whence after accounting vtime

2017-06-29 Thread Frederic Weisbecker
Even though it doesn't have functional consequences, setting the task's new context state after we actually accounted the pending vtime from the old context state makes more sense from a review perspective. vtime_user_exit() is the only function that doesn't follow that rule and that can bug the

[PATCH 2/5] sched: Always set vtime_snap_whence after accounting vtime

2017-06-29 Thread Frederic Weisbecker
Even though it doesn't have functional consequences, setting the task's new context state after we actually accounted the pending vtime from the old context state makes more sense from a review perspective. vtime_user_exit() is the only function that doesn't follow that rule and that can bug the