On 2014年09月17日 17:03, Gautham R Shenoy wrote:
> Hi Lan,
>
> Sorry missed this repost! Couple of comments.
>
Np, Thanks for review :)
> On Fri, Aug 22, 2014 at 04:33:40PM +0800, Lan Tianyu wrote:
>
> [.. snip ..]
>>
>> +static int _cpu_up_with_trace(int cpu)
>> +{
>> +int error;
>> +
>> +
Hi Lan,
Sorry missed this repost! Couple of comments.
On Fri, Aug 22, 2014 at 04:33:40PM +0800, Lan Tianyu wrote:
[.. snip ..]
>
> +static int _cpu_up_with_trace(int cpu)
> +{
> + int error;
> +
> + trace_suspend_resume(TPS("CPU_ON"), cpu, true);
> + error = _cpu_up(cpu, 1);
> +
On 2014年08月30日 08:22, Rafael J. Wysocki wrote:
> On 8/29/2014 5:40 AM, Lan Tianyu wrote:
>> On 2014年08月22日 16:33, Lan Tianyu wrote:
>>> In the current world, all nonboot cpus are enabled serially during
>>> system
>>> resume. System resume sequence is that boot cpu enables nonboot cpu
>>> one by
>>
On 8/29/2014 5:40 AM, Lan Tianyu wrote:
On 2014年08月22日 16:33, Lan Tianyu wrote:
In the current world, all nonboot cpus are enabled serially during system
resume. System resume sequence is that boot cpu enables nonboot cpu one by
one and then resume devices. Before resuming devices, there are few
On 2014年08月22日 16:33, Lan Tianyu wrote:
> In the current world, all nonboot cpus are enabled serially during system
> resume. System resume sequence is that boot cpu enables nonboot cpu one by
> one and then resume devices. Before resuming devices, there are few tasks
> assigned to nonboot cpus aft
In the current world, all nonboot cpus are enabled serially during system
resume. System resume sequence is that boot cpu enables nonboot cpu one by
one and then resume devices. Before resuming devices, there are few tasks
assigned to nonboot cpus after they are brought up. This waste cpu usage.
T
6 matches
Mail list logo
