From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757235Ab3GRIXn (ORCPT ); Thu, 18 Jul 2013 04:23:43 -0400 Received: from merlin.infradead.org ([205.233.59.134]:56806 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757185Ab3GRIXl (ORCPT ); Thu, 18 Jul 2013 04:23:41 -0400 Date: Thu, 18 Jul 2013 10:23:24 +0200 From: Peter Zijlstra To: "Yan, Zheng" Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, eranian@google.com, ak@linux.intel.com Subject: Re: [PATCH] perf, x86: Add Silvermont (22nm Atom) support Message-ID: <20130718082324.GA27075@twins.programming.kicks-ass.net> References: <1374125767-9411-1-git-send-email-zheng.z.yan@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1374125767-9411-1-git-send-email-zheng.z.yan@intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 18, 2013 at 01:36:07PM +0800, Yan, Zheng wrote: > +static struct event_constraint intel_slm_event_constraints[] __read_mostly = > +{ > + FIXED_EVENT_CONSTRAINT(0x00c0, 0), /* INST_RETIRED.ANY */ > + FIXED_EVENT_CONSTRAINT(0x003c, 1), /* CPU_CLK_UNHALTED.CORE */ > + FIXED_EVENT_CONSTRAINT(0x013c, 2), /* CPU_CLK_UNHALTED.REF */ > + FIXED_EVENT_CONSTRAINT(0x0300, 2), /* pseudo CPU_CLK_UNHALTED.REF */ So the normal event 0x13c and the fixed counter 2 are normally _not_ the same. Are they for slm? Are you sure? > + EVENT_CONSTRAINT_END > +};