Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-31 Thread Frederic Weisbecker
2013/1/31 Sedat Dilek : > I still dunno all parts of dynticks and their correlation. > AFAICS they seem to be independent, can't say if it is "complete" with > dynticks-cputime-only. Dynticks cputime and dynticks printk are both standalone and independant. In mainline, both printk and cputime acco

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-31 Thread Sedat Dilek
On Thu, Jan 31, 2013 at 11:12 AM, Frederic Weisbecker wrote: > 2013/1/31 Sedat Dilek : >> On Thu, Jan 31, 2013 at 1:38 AM, Frederic Weisbecker >> wrote: >>> 2013/1/28 Sedat Dilek : On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker wrote: > While remotely reading the cputime of

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-31 Thread Frederic Weisbecker
2013/1/31 Sedat Dilek : > On Thu, Jan 31, 2013 at 1:38 AM, Frederic Weisbecker > wrote: >> 2013/1/28 Sedat Dilek : >>> On Mon, Jan 28, 2013 at 8:04 PM, Frederic Weisbecker >>> wrote: While remotely reading the cputime of a task running in a full dynticks CPU, the values stored in utim

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-30 Thread Sedat Dilek
On Thu, Jan 31, 2013 at 1:38 AM, Frederic Weisbecker wrote: > 2013/1/28 Sedat Dilek : >> On Mon, Jan 28, 2013 at 8:04 PM, 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_

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-30 Thread Frederic Weisbecker
2013/1/28 Sedat Dilek : > On Mon, Jan 28, 2013 at 8:04 PM, 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 <

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-30 Thread Sedat Dilek
On Mon, Jan 28, 2013 at 10:51 PM, Sedat Dilek wrote: > On Mon, Jan 28, 2013 at 8:04 PM, 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

Re: [PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-28 Thread Sedat Dilek
On Mon, Jan 28, 2013 at 8:04 PM, 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

[PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-28 Thread Frederic Weisbecker
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 f

[PATCH 8/8] cputime: Safely read cputime of full dynticks CPUs

2013-01-22 Thread Frederic Weisbecker
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 f