From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753794AbbG0O44 (ORCPT ); Mon, 27 Jul 2015 10:56:56 -0400 Received: from mail-pd0-f178.google.com ([209.85.192.178]:33024 "EHLO mail-pd0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752818AbbG0O4y (ORCPT ); Mon, 27 Jul 2015 10:56:54 -0400 Date: Mon, 27 Jul 2015 20:26:50 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Linux PM list , Linux Kernel Mailing List , Russell King - ARM Linux Subject: Re: [PATCH 5/7] cpufreq: Do not update related_cpus on every policy activation Message-ID: <20150727145650.GG18535@linux> References: <7868353.pEStq1MJ2a@vostro.rjw.lan> <3874727.Jpay9zgokc@vostro.rjw.lan> <3102455.P3lingtaHD@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3102455.P3lingtaHD@vostro.rjw.lan> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27-07-15, 16:06, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The related_cpus mask includes CPUs whose cpufreq_cpu_data per-CPU > pointers have been set to the given policy. Since those pointers > are only set at the policy creation time and unset when the policy > is deleted, the related_cpus should not be updated between those > two operations. > > For this reason, avoid updating it whenever the first of the > "related" CPUs goes online. > > Signed-off-by: Rafael J. Wysocki > --- > drivers/cpufreq/cpufreq.c | 10 +++++----- > 1 file changed, 5 insertions(+), 5 deletions(-) Acked-by: Viresh Kumar -- viresh