Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-12-07 Thread Patrick Bellasi
On 07-Dec 14:54, Viresh Kumar wrote: > On 30-11-17, 16:42, Patrick Bellasi wrote: > > On 30-Nov 17:12, Juri Lelli wrote: > > > Not sure about this though, not my call :). I guess this still helps > > > until we get the DL changes in. > > > > Yes, agree... well Viresh had some concerns about this

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-12-07 Thread Patrick Bellasi
On 07-Dec 14:54, Viresh Kumar wrote: > On 30-11-17, 16:42, Patrick Bellasi wrote: > > On 30-Nov 17:12, Juri Lelli wrote: > > > Not sure about this though, not my call :). I guess this still helps > > > until we get the DL changes in. > > > > Yes, agree... well Viresh had some concerns about this

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-12-07 Thread Viresh Kumar
On 30-11-17, 16:42, Patrick Bellasi wrote: > On 30-Nov 17:12, Juri Lelli wrote: > > Not sure about this though, not my call :). I guess this still helps > > until we get the DL changes in. > > Yes, agree... well Viresh had some concerns about this patch. > Let see what he thinks. And the problem

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-12-07 Thread Viresh Kumar
On 30-11-17, 16:42, Patrick Bellasi wrote: > On 30-Nov 17:12, Juri Lelli wrote: > > Not sure about this though, not my call :). I guess this still helps > > until we get the DL changes in. > > Yes, agree... well Viresh had some concerns about this patch. > Let see what he thinks. And the problem

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
On 30-Nov 17:12, Juri Lelli wrote: > On 30/11/17 16:02, Patrick Bellasi wrote: > > On 30-Nov 14:41, Juri Lelli wrote: > > [...] > > > > If the DL changes (which I shall post again as soon as tip/sched/core is > > > bumped up to 4.15-rc1) get in first, this is going to be useless (as the > > > DL

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
On 30-Nov 17:12, Juri Lelli wrote: > On 30/11/17 16:02, Patrick Bellasi wrote: > > On 30-Nov 14:41, Juri Lelli wrote: > > [...] > > > > If the DL changes (which I shall post again as soon as tip/sched/core is > > > bumped up to 4.15-rc1) get in first, this is going to be useless (as the > > > DL

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Juri Lelli
On 30/11/17 16:02, Patrick Bellasi wrote: > On 30-Nov 14:41, Juri Lelli wrote: [...] > > If the DL changes (which I shall post again as soon as tip/sched/core is > > bumped up to 4.15-rc1) get in first, this is going to be useless (as the > > DL kthread gets ignored by the scheduling class

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Juri Lelli
On 30/11/17 16:02, Patrick Bellasi wrote: > On 30-Nov 14:41, Juri Lelli wrote: [...] > > If the DL changes (which I shall post again as soon as tip/sched/core is > > bumped up to 4.15-rc1) get in first, this is going to be useless (as the > > DL kthread gets ignored by the scheduling class

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
On 30-Nov 14:41, Juri Lelli wrote: > Hi, > > On 30/11/17 11:47, Patrick Bellasi wrote: > > In system where multiple CPUs shares the same frequency domain a small > > workload on a CPU can still be subject to frequency spikes, generated by > > the activation of the sugov's kthread. > > > > Since

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
On 30-Nov 14:41, Juri Lelli wrote: > Hi, > > On 30/11/17 11:47, Patrick Bellasi wrote: > > In system where multiple CPUs shares the same frequency domain a small > > workload on a CPU can still be subject to frequency spikes, generated by > > the activation of the sugov's kthread. > > > > Since

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Juri Lelli
Hi, On 30/11/17 11:47, Patrick Bellasi wrote: > In system where multiple CPUs shares the same frequency domain a small > workload on a CPU can still be subject to frequency spikes, generated by > the activation of the sugov's kthread. > > Since the sugov kthread is a special RT task, which goal

Re: [PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Juri Lelli
Hi, On 30/11/17 11:47, Patrick Bellasi wrote: > In system where multiple CPUs shares the same frequency domain a small > workload on a CPU can still be subject to frequency spikes, generated by > the activation of the sugov's kthread. > > Since the sugov kthread is a special RT task, which goal

[PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
In system where multiple CPUs shares the same frequency domain a small workload on a CPU can still be subject to frequency spikes, generated by the activation of the sugov's kthread. Since the sugov kthread is a special RT task, which goal is just that to activate a frequency transition, it does

[PATCH v3 6/6] cpufreq: schedutil: ignore sugov kthreads

2017-11-30 Thread Patrick Bellasi
In system where multiple CPUs shares the same frequency domain a small workload on a CPU can still be subject to frequency spikes, generated by the activation of the sugov's kthread. Since the sugov kthread is a special RT task, which goal is just that to activate a frequency transition, it does