Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp4457071ybe; Mon, 9 Sep 2019 09:30:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqy/cnr0b94ycJANVtGZ5LxNIfGbao3T0/tZcEhcHqtB/GYCCiy6kdHKVB4dPaT8rGePjkPR X-Received: by 2002:a17:906:1183:: with SMTP id n3mr12106274eja.236.1568046644251; Mon, 09 Sep 2019 09:30:44 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568046644; cv=none; d=google.com; s=arc-20160816; b=hL4cY7wqqjGLBNqSbxBSEpXaBeEbzVsmKuZA7FQffwmshTFyQf5fUQ8ZazGd4NznPE z5fUiFwzg903PAQICmSTd2But/L17EzvyEunhwo4zi+txnq01nc/6shWmzYyhGVu7UWH rvA7IRsTPwVyGFu3xjiotBo89tByZaTUevYJYl38GpBrybbfpFRpeNPSVTUWUgn8ZT0Y hHZaN5jZM+dCvFoz7W3MB8vDOkyjRIdkKbO73UvkcmV96oSH0JinAc5gtyP55AxHGLYq yeOJ/1o6IyINxiupzyXpiMwTcxrcoRQlX3WlucjYEg1U1Wov564hfzlFa5+LF/uy5mez AIEw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=fhHZ4ji+GGLxXf+KhCHKVc2xiiILk3SNJO/ElLm5e4I=; b=XT56wnlAiRl9AXF/g9kR8ANEnMB3HwHWfw0fTc4krLnyZTSYAojcc/Fvr0sM9AXNxm yX7lp+PahCFPhzFUmyOEa0d9InbGeyPYs6qXLb4ITjeshVIxkeK4WUS5P5m4Dpf7iOO4 BzXO/eEUQvR1GbjXC2CXH8Qa5vd9ccMAJN9Qybsh5O1b32NJUcx3fiSJaTG0U5SVkdWf K8IKC7SBRcuRGoa6sUJKvGgBbyGP1Hn/NNnhEXjEdvO1rIOxSkrHDrR9xb1fbhma0zrf quANR8YAaLpEYvmEVQn8B/9hECJFTOINE1cHiwMkx0BowrgKfx/ytukLvqU80LUJY7MB QUPQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x22si7911158edi.382.2019.09.09.09.30.20; Mon, 09 Sep 2019 09:30:44 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728182AbfIHOnT (ORCPT + 99 others); Sun, 8 Sep 2019 10:43:19 -0400 Received: from mga17.intel.com ([192.55.52.151]:60667 "EHLO mga17.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725928AbfIHOnT (ORCPT ); Sun, 8 Sep 2019 10:43:19 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Sep 2019 07:43:19 -0700 X-IronPort-AV: E=Sophos;i="5.64,481,1559545200"; d="scan'208";a="184975914" Received: from spandruv-mobl.amr.corp.intel.com ([10.252.4.36]) by fmsmga007-auth.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Sep 2019 07:43:17 -0700 Message-ID: Subject: Re: [PATCH 2/2] tools/power/x86/intel-speed-select: Display core count for bucket From: Srinivas Pandruvada To: Andy Shevchenko Cc: Andy Shevchenko , Prarit Bhargava , David Arcari , Linux Kernel Mailing List , Platform Driver Date: Sun, 08 Sep 2019 07:43:14 -0700 In-Reply-To: References: <20190905233748.6822-1-srinivas.pandruvada@linux.intel.com> <20190905233748.6822-2-srinivas.pandruvada@linux.intel.com> <780a3faf-9e44-64f4-a354-bdee39af3af5@redhat.com> <20190906134655.GU2680@smile.fi.intel.com> <6b576770a4bbe6c24ea524083dec5a16bf3c9e94.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-1.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2019-09-07 at 21:18 +0300, Andy Shevchenko wrote: > On Fri, Sep 6, 2019 at 10:47 PM Srinivas Pandruvada > wrote: > > > > On Fri, 2019-09-06 at 07:50 -0700, Srinivas Pandruvada wrote: > > > On Fri, 2019-09-06 at 16:46 +0300, Andy Shevchenko wrote: > > > > On Fri, Sep 06, 2019 at 05:39:54AM -0400, Prarit Bhargava > > > > wrote: > > > > > On 9/5/19 7:37 PM, Srinivas Pandruvada wrote: > > > > > > Read the bucket and core count relationship via MSR and > > > > > > display > > > > > > when displaying turbo ratio limits. > > > > > > + ret = isst_send_msr_command(cpu, 0x1ae, 0, > > > > > > buckets_info); > > > > > > > > > > ^^^ you can get rid of the magic number 0x1ae by doing (sorry > > > > > for > > > > > the cut-and-paste) > > > > > > > > > > diff --git a/tools/power/x86/intel-speed-select/Makefile > > > > > b/tools/power/x86/intel > > > > > index 12c6939dca2a..087d802ad844 100644 > > > > > --- a/tools/power/x86/intel-speed-select/Makefile > > > > > +++ b/tools/power/x86/intel-speed-select/Makefile > > > > > @@ -15,6 +15,8 @@ endif > > > > > MAKEFLAGS += -r > > > > > > > > > > override CFLAGS += -O2 -Wall -g -D_GNU_SOURCE > > > > > -I$(OUTPUT)include > > > > > +override CFLAGS += -I../../../include > > > > > +override CFLAGS += > > > > > -DMSRHEADER='"../../../../arch/x86/include/asm/msr-index.h"' > > > > > > No, we can't use msr_index. > > > > This comment was meant for use of /dev/cpu/X/msr not msr_index. > > I didn't want to bring in dependency on msr-index.h for couple of 2 > > MSRs and the names in msr-index.h doesn't really reflect the actual > > processing, they are doing. For example MSR_TURBO_RATIO_LIMIT1 for > > 0x1ae. The definition of 0x1AE is different on cpu model 0x55 and > > beyond. > > > > > > > It seems not applicable on top of tools patch series I had applied > before. I have rebased on the top of your review branch and resent. Thanks, Srinivas > > > > > > > > > I guess it can be done in more neat way. > > > > > > > > > As I've been looking at this code I have been wondering why > > > > > didn't > > > > > you just use > > > > > the standard /dev/cpu/X/msr interface that other x86 power > > > > > utilities (turbostat, > > > > > x86_energy_perf_policy) use? Implementing msr_read() is > > > > > trivial > > > > > (warning > > > > > untested and uncompiled code) > > > > > > No. We can't. The MSR interface is disabled on several > > > distribution > > > and > > > platforms with secured boot. So some special MSRs are only > > > allowed > > > via > > > this IOCTL interface. > > > > > > Thanks, > > > Srinivas > > > > > > > > > > > > > > Actually good point! > > > > > >