public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yong Wang <yong.y.wang@linux.intel.com>
To: eranian@gmail.com
Cc: "Wang, Yong Y" <yong.y.wang@intel.com>,
	Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: perf_counter Atom patch
Date: Tue, 23 Jun 2009 15:59:59 +0800	[thread overview]
Message-ID: <20090623075959.GA23534@ywang-moblin2.bj.intel.com> (raw)
In-Reply-To: <7c86c4470906230045k578bc146wa0e09e4094d937a5@mail.gmail.com>

On Tue, Jun 23, 2009 at 09:45:03AM +0200, stephane eranian wrote:
>
> Unfortunately, I don't have a N270 to compare with your results.
> We need to verify whether or not N270 implements the fixed counters.
> Does it report architected perfmon v3 or v1?
> 

All Atom processors report perfmon v3 as specified in SDM. N270 is no
exception.

> > The return value of CPUID(0xa) is indeed bogus, too and there is another quirk for that in
> > intel_pmu_init() in arch/x86/kernel/cpu/perf_counter.c
> >
> > x86_pmu.num_counters_fixed ?? ?? ??= max((int)edx.split.num_counters_fixed, 3);
> >
> > Is this what you were talking about?
> 
> Not quite, because with the max() you'd have a problem on Intel Core
> Duo/Solo processors
> as they do implement the first generation of architected perfmon and
> that one did not have
> fixed counters. So you'd have to special case family=6 model=14.

That has been taken into account actually. Only perfmon v2 and above are
supported as you see in intel_pmu_init().

	if (version < 2)
		return -ENODEV;


  reply	other threads:[~2009-06-23  8:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 20:26 perf_counter Atom patch stephane eranian
2009-06-23  3:38 ` Wang, Yong Y
2009-06-23  7:45   ` stephane eranian
2009-06-23  7:59     ` Yong Wang [this message]
2009-06-23  8:27       ` stephane eranian
2009-06-23  8:34         ` Yong Wang
2009-06-23  9:10           ` Peter Zijlstra
2009-06-23  9:40             ` stephane eranian
2009-06-23  8:40         ` stephane eranian
2009-06-23  8:53           ` Yong Wang
2009-06-23  9:19             ` stephane eranian
2009-06-23  9:47             ` Ingo Molnar
2009-06-24  2:19               ` Yong Wang
2009-06-24  8:52                 ` Ingo Molnar
2009-06-25 10:39                   ` stephane eranian
2009-06-23  5:59 ` Wang, Yong Y

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090623075959.GA23534@ywang-moblin2.bj.intel.com \
    --to=yong.y.wang@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=yong.y.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox