Received: by 2002:a4a:311b:0:0:0:0:0 with SMTP id k27-v6csp4624569ooa; Tue, 14 Aug 2018 08:22:28 -0700 (PDT) X-Google-Smtp-Source: AA+uWPy9Y4dMNKAxBx908dBEtqatCsVDoWaTo9ggSpPF2cGrMSd09p7bWOKpvwINmhN1CUZ0nef6 X-Received: by 2002:a63:2404:: with SMTP id k4-v6mr21349429pgk.191.1534260148000; Tue, 14 Aug 2018 08:22:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534260147; cv=none; d=google.com; s=arc-20160816; b=br7tJXBgDc5S1L8d45lo/l8FI6D7x+u/zt7O2uYW/x85afeN3XjMawwAvAwXyT8/Ee NqggUQLKpLdeKK16Z2tVe5H5xHNrsJck3uee/BzHCMMboMefZSd5/xlqu2vMfaaaItE9 M0sY4iL6wo4fCgHvjIOAFAZSUYwjnGTGcrmZFH+yLWixH04AJS3chUnD+x3fbZ6LcbTV r+TpoRtR+T8sKiRtfoNDk3p5Eriml8cjaYm1BrVpsLXmBNri7XBk9motnjpu+cgUS2xI OJ/sGpLlNXzCKB2lZx4O1HV/sHI1hdeGP1CiPRkMXZXZXg6KTPMhpBQxt0sCpPsbBeG1 YjXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=MGV5OM6bWROJ9bGh9ReI6R/pYf3ebgXgF46CAalq1p4=; b=DwEE54JfxPp48yIQLItchClA/279zl2IZc1h2IjW7VwJF6vwwXTDnXdrR9Q4EWpe+M 4A+HWjUW7MvyS6VOwwYv2gpzpOhklf4E4GS15OenHrWAWicaK5n9f5ARhLAub+vjHrzI 72mfqJMDWUZqggnYL+T1NLlpcsf+P4n2mGdsoSWzNMdqPVR2za+XnDbwXAeXNMkIdsGF ptg8SVIF1SESJwmQxOZ0l8M4UOyFCIy8A6mAMmonYIXyoRjhTZrxUbmIOwoGjwHpA7o4 Fxx/14XKwvVSunQyK0+Zv+h52nW5HK7hHDvDK1munTGmh3jLI/nqgbd7xXfjYxiT29B8 FT/Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q129-v6si20231549pga.217.2018.08.14.08.22.12; Tue, 14 Aug 2018 08:22:27 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732384AbeHNSI6 (ORCPT + 99 others); Tue, 14 Aug 2018 14:08:58 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:44966 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730759AbeHNSI6 (ORCPT ); Tue, 14 Aug 2018 14:08:58 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8650C80D; Tue, 14 Aug 2018 08:21:22 -0700 (PDT) Received: from e110439-lin (e110439-lin.emea.arm.com [10.4.12.126]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B7ACF3F5D0; Tue, 14 Aug 2018 08:21:19 -0700 (PDT) Date: Tue, 14 Aug 2018 16:21:17 +0100 From: Patrick Bellasi To: Pavan Kondeti Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Tejun Heo , "Rafael J . Wysocki" , Viresh Kumar , Vincent Guittot , Paul Turner , Dietmar Eggemann , Morten Rasmussen , Juri Lelli , Todd Kjos , Joel Fernandes , Steve Muckle , Suren Baghdasaryan Subject: Re: [PATCH v3 02/14] sched/core: uclamp: map TASK's clamp values into CPU's clamp groups Message-ID: <20180814152117.GF2605@e110439-lin> References: <20180806163946.28380-1-patrick.bellasi@arm.com> <20180806163946.28380-3-patrick.bellasi@arm.com> <20180814112509.GB2661@codeaurora.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180814112509.GB2661@codeaurora.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pavan, On 14-Aug 16:55, Pavan Kondeti wrote: > On Mon, Aug 06, 2018 at 05:39:34PM +0100, Patrick Bellasi wrote: > I see that we drop reference on the previous clamp group when a task changes > its clamp limits. What about exiting tasks which claimed clamp groups? should > not we drop the reference? Yes, you right... when a task ends we are not currently releasing the reference to its (eventually defined) task-specific clamp value! Thanks for pointing this out... I'll fix this on the next posting! -- #include Patrick Bellasi