From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965606AbcA1J4G (ORCPT ); Thu, 28 Jan 2016 04:56:06 -0500 Received: from e23smtp05.au.ibm.com ([202.81.31.147]:51410 "EHLO e23smtp05.au.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964979AbcA1Jz7 (ORCPT ); Thu, 28 Jan 2016 04:55:59 -0500 X-IBM-Helo: d23dlp02.au.ibm.com X-IBM-MailFrom: shilpa.bhat@linux.vnet.ibm.com X-IBM-RcptTo: linux-api@vger.kernel.org;linux-kernel@vger.kernel.org;linux-pm@vger.kernel.org Message-ID: <56A9E56C.1050505@linux.vnet.ibm.com> Date: Thu, 28 Jan 2016 15:24:52 +0530 From: Shilpasri G Bhat User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Viresh Kumar CC: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, rjw@rjwysocki.net, linux-pm@vger.kernel.org, pc@us.ibm.com, anton@samba.org, ego@linux.vnet.ibm.com, shreyas@linux.vnet.ibm.com, bsingharora@gmail.com, mpe@ellerman.id.au, linux-api@vger.kernel.org Subject: Re: [PATCH v7 6/6] cpufreq: powernv: Add sysfs attributes to show throttle stats References: <1453965941-7363-1-git-send-email-shilpa.bhat@linux.vnet.ibm.com> <1453965941-7363-7-git-send-email-shilpa.bhat@linux.vnet.ibm.com> <20160128084041.GK3935@vireshk> <56A9E136.8090900@linux.vnet.ibm.com> <20160128094146.GO3935@vireshk> In-Reply-To: <20160128094146.GO3935@vireshk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16012809-0017-0000-0000-000002ACA7A1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 01/28/2016 03:11 PM, Viresh Kumar wrote: > On 28-01-16, 15:06, Shilpasri G Bhat wrote: >> No these stats are not per-policy. They are per-chip. The throttle event is >> common for all cores in the chip. > > How do you define a chip? And how is it different then the group of > CPUs represented by the policy ? > Chip is a group of policies. Hmm yes I see your point. We anyways maintain frequency stats which is per-policy. We might as well have throttle stats exported per-policy which points to per-chip data.