Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-10-03 Thread Daniel Lezcano
On 10/03/2013 06:38 AM, Viresh Kumar wrote: On 1 October 2013 00:07, Daniel Lezcano wrote: Interesting, thanks for the pointer. So, should I keep this patch with SRCU? IMHO, we should, for now, keep the code as it is and then focus on the lock/refcount for drivers in a separate series.

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-10-02 Thread Viresh Kumar
On 1 October 2013 00:07, Daniel Lezcano wrote: > Interesting, thanks for the pointer. So, should I keep this patch with SRCU? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-09-30 Thread Daniel Lezcano
On 09/28/2013 11:33 PM, Paul E. McKenney wrote: On Thu, Sep 26, 2013 at 10:19:14AM +0200, Daniel Lezcano wrote: On 09/26/2013 08:17 AM, Viresh Kumar wrote: On 26 September 2013 04:00, Daniel Lezcano wrote: If you introduce a list, you will have to introduce a lock to protect it. I missed it

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-09-28 Thread Paul E. McKenney
On Thu, Sep 26, 2013 at 10:19:14AM +0200, Daniel Lezcano wrote: > On 09/26/2013 08:17 AM, Viresh Kumar wrote: > >On 26 September 2013 04:00, Daniel Lezcano wrote: > >>If you introduce a list, you will have to introduce a lock to protect > >>it. > > > >I missed it, should have added that :) > > > >

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-09-26 Thread Daniel Lezcano
On 09/26/2013 08:17 AM, Viresh Kumar wrote: On 26 September 2013 04:00, Daniel Lezcano wrote: If you introduce a list, you will have to introduce a lock to protect it. I missed it, should have added that :) This lock will be in the fast path cpuidle_idle_call with the get_driver function an

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-09-25 Thread Viresh Kumar
On 26 September 2013 04:00, Daniel Lezcano wrote: > If you introduce a list, you will have to introduce a lock to protect > it. I missed it, should have added that :) > This lock will be in the fast path cpuidle_idle_call with the > get_driver function and conforming to the comment: "NOTE: no lo

Re: [PATCH 19/21] cpuidle: create list of registered drivers

2013-09-25 Thread Daniel Lezcano
On 09/22/2013 03:21 AM, Viresh Kumar wrote: > Currently we have multiple definitions of few routines based on following > config > option: CONFIG_CPU_IDLE_MULTIPLE_DRIVERS. > > These are present to save space by not creating per-cpu variable for platforms > which need only one cpuidle driver to b

[PATCH 19/21] cpuidle: create list of registered drivers

2013-09-21 Thread Viresh Kumar
Currently we have multiple definitions of few routines based on following config option: CONFIG_CPU_IDLE_MULTIPLE_DRIVERS. These are present to save space by not creating per-cpu variable for platforms which need only one cpuidle driver to be registered for all CPUs. But this setup has a problem.