On 30/03/17 22:22, Rafael J. Wysocki wrote:
> On Thursday, March 30, 2017 08:50:11 AM Vikram Mulukutla wrote:
> >
> > > OK
> > >
> > > So there are two pieces here.
> > >
> > > One is that if we want *all* drivers to work with schedutil, we need to
> > > keep
> > > the kthread for the ones
On 30/03/17 22:22, Rafael J. Wysocki wrote:
> On Thursday, March 30, 2017 08:50:11 AM Vikram Mulukutla wrote:
> >
> > > OK
> > >
> > > So there are two pieces here.
> > >
> > > One is that if we want *all* drivers to work with schedutil, we need to
> > > keep
> > > the kthread for the ones
On Thursday, March 30, 2017 08:50:11 AM Vikram Mulukutla wrote:
>
> > OK
> >
> > So there are two pieces here.
> >
> > One is that if we want *all* drivers to work with schedutil, we need to
> > keep
> > the kthread for the ones that will never be reworked (because nobody
> > cares
> > etc).
On Thursday, March 30, 2017 08:50:11 AM Vikram Mulukutla wrote:
>
> > OK
> >
> > So there are two pieces here.
> >
> > One is that if we want *all* drivers to work with schedutil, we need to
> > keep
> > the kthread for the ones that will never be reworked (because nobody
> > cares
> > etc).
OK
So there are two pieces here.
One is that if we want *all* drivers to work with schedutil, we need to
keep
the kthread for the ones that will never be reworked (because nobody
cares
etc). But then perhaps the kthread implementation may be left alone
(because
nobody cares etc).
The
OK
So there are two pieces here.
One is that if we want *all* drivers to work with schedutil, we need to
keep
the kthread for the ones that will never be reworked (because nobody
cares
etc). But then perhaps the kthread implementation may be left alone
(because
nobody cares etc).
The
On Tue, Mar 28, 2017 at 11:29:31AM +0200, Vincent Guittot wrote:
> On 27 March 2017 at 18:50, Peter Zijlstra wrote:
> > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> >> Worker kthread needs to be able to change frequency for all other
> >> threads.
> >>
> >>
On Tue, Mar 28, 2017 at 11:29:31AM +0200, Vincent Guittot wrote:
> On 27 March 2017 at 18:50, Peter Zijlstra wrote:
> > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> >> Worker kthread needs to be able to change frequency for all other
> >> threads.
> >>
> >> Make it special, just
On 27 March 2017 at 18:50, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
>> Worker kthread needs to be able to change frequency for all other
>> threads.
>>
>> Make it special, just under STOP class.
>
> *yuck* ;-)
>
> So imagine our
On 27 March 2017 at 18:50, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
>> Worker kthread needs to be able to change frequency for all other
>> threads.
>>
>> Make it special, just under STOP class.
>
> *yuck* ;-)
>
> So imagine our I2C/SPI bus is 'busy' and
On Mon, Mar 27, 2017 at 07:37:39PM +0200, Rafael J. Wysocki wrote:
> One is that if we want *all* drivers to work with schedutil, we need to keep
> the kthread for the ones that will never be reworked (because nobody cares
> etc). But then perhaps the kthread implementation may be left alone
On Mon, Mar 27, 2017 at 07:37:39PM +0200, Rafael J. Wysocki wrote:
> One is that if we want *all* drivers to work with schedutil, we need to keep
> the kthread for the ones that will never be reworked (because nobody cares
> etc). But then perhaps the kthread implementation may be left alone
On Mon, Mar 27, 2017 at 06:50:11PM +0200, Peter Zijlstra wrote:
> Taken together this seems to suggest we can rework cpufreq drivers to
> function in-context, either directly push the packet on the bus if
> available, or queue it and let whoever owns it sort it without blocking.
Note that this
On Mon, Mar 27, 2017 at 06:50:11PM +0200, Peter Zijlstra wrote:
> Taken together this seems to suggest we can rework cpufreq drivers to
> function in-context, either directly push the packet on the bus if
> available, or queue it and let whoever owns it sort it without blocking.
Note that this
On Monday, March 27, 2017 06:13:36 PM Juri Lelli wrote:
> On 27/03/17 19:05, Rafael J. Wysocki wrote:
> > On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> > > On 27/03/17 18:50, Peter Zijlstra wrote:
> > > > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > > > Worker
On Monday, March 27, 2017 06:13:36 PM Juri Lelli wrote:
> On 27/03/17 19:05, Rafael J. Wysocki wrote:
> > On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> > > On 27/03/17 18:50, Peter Zijlstra wrote:
> > > > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > > > Worker
On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> On 27/03/17 18:50, Peter Zijlstra wrote:
> > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > Worker kthread needs to be able to change frequency for all other
> > > threads.
> > >
> > > Make it special, just under STOP
On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> On 27/03/17 18:50, Peter Zijlstra wrote:
> > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > Worker kthread needs to be able to change frequency for all other
> > > threads.
> > >
> > > Make it special, just under STOP
On 27/03/17 19:05, Rafael J. Wysocki wrote:
> On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> > On 27/03/17 18:50, Peter Zijlstra wrote:
> > > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > > Worker kthread needs to be able to change frequency for all other
> > > >
On 27/03/17 19:05, Rafael J. Wysocki wrote:
> On Monday, March 27, 2017 06:01:34 PM Juri Lelli wrote:
> > On 27/03/17 18:50, Peter Zijlstra wrote:
> > > On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > > > Worker kthread needs to be able to change frequency for all other
> > > >
On 27/03/17 18:50, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > Worker kthread needs to be able to change frequency for all other
> > threads.
> >
> > Make it special, just under STOP class.
>
> *yuck* ;-)
>
Eh, I know. :/
> So imagine our I2C/SPI
On 27/03/17 18:50, Peter Zijlstra wrote:
> On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> > Worker kthread needs to be able to change frequency for all other
> > threads.
> >
> > Make it special, just under STOP class.
>
> *yuck* ;-)
>
Eh, I know. :/
> So imagine our I2C/SPI
On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> Worker kthread needs to be able to change frequency for all other
> threads.
>
> Make it special, just under STOP class.
*yuck* ;-)
So imagine our I2C/SPI bus is 'busy' and its mutex taken, then this
'soecial' task will need to boost
On Fri, Mar 24, 2017 at 02:08:58PM +, Juri Lelli wrote:
> Worker kthread needs to be able to change frequency for all other
> threads.
>
> Make it special, just under STOP class.
*yuck* ;-)
So imagine our I2C/SPI bus is 'busy' and its mutex taken, then this
'soecial' task will need to boost
Worker kthread needs to be able to change frequency for all other
threads.
Make it special, just under STOP class.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Rafael J. Wysocki
Cc:
Worker kthread needs to be able to change frequency for all other
threads.
Make it special, just under STOP class.
Signed-off-by: Juri Lelli
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Rafael J. Wysocki
Cc: Viresh Kumar
Cc: Luca Abeni
Cc: Claudio Scordino
---
include/linux/sched.h
26 matches
Mail list logo