From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S932915AbdBVOzU (ORCPT <rfc822;w@1wt.eu>);
        Wed, 22 Feb 2017 09:55:20 -0500
Received: from mail-pg0-f45.google.com ([74.125.83.45]:35476 "EHLO
        mail-pg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S932778AbdBVOzJ (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 22 Feb 2017 09:55:09 -0500
Subject: Re: 9908859acaa9 cpuidle/menu: add per CPU PM QoS resume latency
 consideration
To: Peter Zijlstra <peterz@infradead.org>
References: <1487768197.27533.5.camel@gmx.de>
 <20170222131218.GS6515@twins.programming.kicks-ass.net>
 <1487769542.4487.2.camel@gmx.de>
 <ac73da0c-4a0d-c36b-9d5a-fe88de3a1acf@linaro.org>
 <20170222143910.GV6515@twins.programming.kicks-ass.net>
Cc: Mike Galbraith <efault@gmx.de>, LKML <linux-kernel@vger.kernel.org>,
        "Rafael J. Wysocki" <rjw@rjwysocki.net>,
        Rik van Riel <riel@redhat.com>
From: Alex Shi <alex.shi@linaro.org>
Message-ID: <47a10932-b485-cf3f-bf39-ccf3026a960f@linaro.org>
Date: Wed, 22 Feb 2017 22:55:04 +0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.3.0
MIME-Version: 1.0
In-Reply-To: <20170222143910.GV6515@twins.programming.kicks-ass.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> 
> 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! :)