Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755680AbbFOR0R (ORCPT ); Mon, 15 Jun 2015 13:26:17 -0400 Received: from mail-qc0-f172.google.com ([209.85.216.172]:35826 "EHLO mail-qc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753425AbbFOR0H (ORCPT ); Mon, 15 Jun 2015 13:26:07 -0400 From: Vince Weaver X-Google-Original-From: Vince Weaver Date: Mon, 15 Jun 2015 13:32:01 -0400 (EDT) To: Jacob Pan cc: LKML , Peter Zijlstra , "H. Peter Anvin" , Stephane Eranian , Paul Mackerras , Andi Kleen , Thomas Gleixner , Arnaldo Carvalho de Melo Subject: Re: [PATCH v3] perf/rapl: support per domain energy unit Message-ID: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1195 Lines: 28 On Thu, 26 Mar 2015, Jacob Pan wrote: > RAPL energy hardware unit can vary within a single CPU package, e.g. > HSW server DRAM has a fixed energy unit of 15.3 uJ (2^-16) whereas > the unit on other domains can be enumerated from power unit MSR. > There might be other variations in the future, this patch adds > per cpu model quirk to allow special handling of certain cpus. So I have a Desktop Haswell machine (model 60) that is instrumented to measure actual DRAM power at the DIMM (with a sense resistor). We are consistently getting RAPL results roughly a factor of 2 smaller than the actual, measured results. Does desktop Haswell have a similar units issue to Haswell-EP? I wasted a bunch of time trying to decode the DRAM_ENERGY_SCALEFACTOR_MCHBAR values described in the Desktop 4th Generation Intel Core Processor Family datasheet but possibly that value in the MCHBAR is unrelated to the one exported by the RAPL interface. Vince -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/