14 Nov
2016
14 Nov
'16
11:30 a.m.
On 14-11-16, 09:36, Viresh Kumar wrote:
On 13-11-16, 15:46, Rafael J. Wysocki wrote:
That's only going to happen in the next patch, though, right? It wouldn't hurt to write that in the changelog too.
Sure.
Besides, I'm not actually sure if starting/stopping the kthread in sugov_policy_alloc/free() is a good idea. It sort of conflates the allocation of memory with kthread creation. Any chance to untangle that?
Hmm, so either I can create two new routines for the thread and call them along with alloc/free. Or I can rename the alloc/free routines and keep this patch as is.
I have created separate routines in my new version (which I will send tomorrow).
--
viresh