[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47a10932-b485-cf3f-bf39-ccf3026a960f@linaro.org>
Date: Wed, 22 Feb 2017 22:55:04 +0800
From: Alex Shi <alex.shi@...aro.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Mike Galbraith <efault@....de>,
LKML <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Rik van Riel <riel@...hat.com>
Subject: Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency
consideration
>
> Its not hard; spinlock_t ends up being a mutex, and this is ran from the
> idle thread. What thread do you think we ought to run when we block
> idle?
>
Straight right.
Thanks for explanations! :)
Powered by blists - more mailing lists