From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753739AbcBGJU2 (ORCPT ); Sun, 7 Feb 2016 04:20:28 -0500 Received: from mail-pf0-f174.google.com ([209.85.192.174]:35805 "EHLO mail-pf0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752918AbcBGJUW (ORCPT ); Sun, 7 Feb 2016 04:20:22 -0500 Date: Sun, 7 Feb 2016 14:50:19 +0530 From: Viresh Kumar To: "Rafael J. Wysocki" Cc: Linux PM list , Linux Kernel Mailing List , Peter Zijlstra , Srinivas Pandruvada , Juri Lelli , Steve Muckle , Thomas Gleixner Subject: Re: [PATCH 3/3 v4] cpufreq: governor: Replace timers with utilization update callbacks Message-ID: <20160207092019.GB6112@vireshk> References: <3071836.JbNxX8hU6x@vostro.rjw.lan> <2546395.Be1INkvQBN@vostro.rjw.lan> <1486401.1RcnnVKZNP@vostro.rjw.lan> <2848076.UWJmIl2O1K@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2848076.UWJmIl2O1K@vostro.rjw.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06-02-16, 04:40, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > Instead of using a per-CPU deferrable timer for queuing up governor > work items, register a utilization update callback that will be > invoked from the scheduler on utilization changes. > > The sampling rate is still the same as what was used for the > deferrable timers and the added irq_work overhead should be offset by > the eliminated timers overhead, so in theory the functional impact of > this patch should not be significant. > > Signed-off-by: Rafael J. Wysocki > --- > > Updated after the recent discussion with Viresh. > > Changes from v3: > - The completion used for irq_work synchronization replaced with irq_work_sync() > in gov_cancel_work(). > - update_sampling_rate() now modifies shared->sample_delay_ns for all CPUs > where it matters directly with a big fat comment explaining why this is > actually OK. > - The above means the time_stamp field in struct cpu_common_dbs_info is not > necessary any more, so it is dropped. > - A build error for !CONFIG_SMP is addressed (hopefully effectively). > > This version was lightly tested on an x86 laptop. Awesome work Rafael, this looks really good now. Acked-by: Viresh Kumar -- viresh