From: Dietmar Hahn Subject: Re: [PATCH 3/3 v2] vpmu intel: Dump vpmu infos in 'q' keyhandler Date: Mon, 08 Apr 2013 11:39:58 +0200 Message-ID: <1477885.LjZmHHAyZ8@amur> References: <8751926.IvtI3fQmuJ@amur> <1614708.69dJLtaETJ@amur> <20130405133338.GC20093@phenom.dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20130405133338.GC20093@phenom.dumpdata.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org Cc: Eddie Dong , suravee.suthikulpanit@amd.com, Jun Nakajima , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org Am Freitag 05 April 2013, 09:33:38 schrieb Konrad Rzeszutek Wilk: > On Thu, Apr 04, 2013 at 02:10:32PM +0200, Dietmar Hahn wrote: > > Am Donnerstag 28 M=E4rz 2013, 14:01:10 schrieb Dietmar Hahn: > > > + /* > > > + * The configuration of the fixed counter is 4 bits each in the > > > + * MSR_CORE_PERF_FIXED_CTR_CTRL. > > > + */ > > > + val =3D core2_vpmu_cxt->ctrls[MSR_CORE_PERF_FIXED_CTR_CTRL_IDX]; > > > + for ( i =3D 0; i < core2_fix_counters.num; i++ ) > > > + { > > > + if ( core2_vpmu_cxt->pmu_enable->fixed_ctr_enable[i] ) > > > + printk(" fixed_%d: 0x%016lx ctrl: 0x%lx\n", > > > + i, core2_vpmu_cxt->fix_counters[i], > > > + val & FIXED_CTR_CTRL_MASK); > > > + val >>=3D FIXED_CTR_CTRL_BITS; > = > This is a bit odd? Was it meant to be on the same line as 'printk'? Sorry, this was mixing of tabs and spaces, will send an update. Thanks. Dietmar. -- = Company details: http://ts.fujitsu.com/imprint.html