mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: stephane eranian <eranian@googlemail.com>
To: yong.y.wang@intel.com
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>,
	Paul Mackerras <paulus@samba.org>
Subject: perf_counter Atom patch
Date: Mon, 22 Jun 2009 22:26:15 +0200	[thread overview]
Message-ID: <7c86c4470906221326j6edbf9f3g5d65e96d86aaf7ab@mail.gmail.com> (raw)

Hi,


You recently submitted a patch for perf_counter to disable
use of fixed counters on Atom because you claim they do
not work.

--------------------------------------------------------------------------------------
author	Yong Wang <yong.y.wang@linux.intel.com>
Fri, 12 Jun 2009 08:08:55 +0000 (16:08 +0800)
committer	Ingo Molnar <mingo@elte.hu>
Fri, 12 Jun 2009 11:48:32 +0000 (13:48 +0200)
commit	dff5da6d09daaab40a8741dce0ed3c2e94079de2
tree	c1f4ce70e4a566a231ba00c775de4e96fb8acb39
parent	faafec1e61e61d350248af2a7e5f047606adab6e
perf_counter/x86: Add a quirk for Atom processors

The fixed-function performance counters do not work on current Atom
processors. Use the general-purpose ones instead.
--------------------------------------------------------------------------------------


I would like to better understand what makes you think
this is the case.

Perfmon is working on Atom and there, fixed counters work perfectly:
$ head -6 /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 28
model name	: Intel(R) Atom(TM) CPU  230   @ 1.60GHz
stepping	: 2
...
$ pfmon -v --us-c -e
unhalted_core_cycles,unhalted_reference_cycles,instructions_retired
noploop 10
[FIXED_CTRL(pmc16)=0xaaa pmi0=1 en0=0x2 any0=0 pmi1=1 en1=0x2 any1=0
pmi2=1 en2=0x2 any2=0] INSTRUCTIONS_RETIRED UNHALTED_CORE_CYCLES
UNHALTED_REFERENCE_CYCLES
[FIXED_CTR0(pmd16)]
[FIXED_CTR1(pmd17)]
[FIXED_CTR2(pmd18)]
noploop for 10 seconds
15,902,604,169 UNHALTED_CORE_CYCLES
15,902,586,180 UNHALTED_REFERENCE_CYCLES
7,941,842,505 INSTRUCTIONS_RETIRED


I seem to recall that what may be bogus on Atom is what is returned by
CPUID(0xa)
for the fixed counters. But they are there and they work. Thus, I
believe, the quirk
should be  at the location where CPUID(0xa) is invoked not where you've put it.

             reply	other threads:[~2009-06-22 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 20:26 stephane eranian [this message]
2009-06-23  3:38 ` Wang, Yong Y
2009-06-23  7:45   ` stephane eranian
2009-06-23  7:59     ` Yong Wang
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=7c86c4470906221326j6edbf9f3g5d65e96d86aaf7ab@mail.gmail.com \
    --to=eranian@googlemail.com \
    --cc=a.p.zijlstra@chello.nl \
    --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

all inboxes | Powered by JetHome®