From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764756AbdAJE3D (ORCPT ); Mon, 9 Jan 2017 23:29:03 -0500 Received: from mail-pf0-f176.google.com ([209.85.192.176]:34602 "EHLO mail-pf0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103AbdAJE3C (ORCPT ); Mon, 9 Jan 2017 23:29:02 -0500 Date: Tue, 10 Jan 2017 09:58:58 +0530 From: Viresh Kumar To: Stephen Boyd Cc: Rafael Wysocki , Viresh Kumar , Nishanth Menon , linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, Vincent Guittot Subject: Re: [PATCH 09/12] PM / OPP: Move away from RCU locking Message-ID: <20170110042858.GD6332@vireshk-i7> References: <2141b49d888d7b60ff317256a559ab78c1448a03.1481106919.git.viresh.kumar@linaro.org> <20170109235727.GA17126@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170109235727.GA17126@codeaurora.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09-01-17, 15:57, Stephen Boyd wrote: > I suppose this is one thing RCU was being used for, marking OPPs > available and then having these "getter" APIs fail if the OPPs go > away. But that was never right because the OPP could have been > made unavailable after this function returned and things still > wouldn't work. Right, it was all so confusing with RCUs in OPP library :) -- viresh