mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@linux.intel.com>
Cc: Corey Ashford <cjashfor@linux.vnet.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Pekka Enberg <penberg@kernel.org>,
	Vince Weaver <vweaver1@eecs.utk.edu>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Stephane Eranian <eranian@gmail.com>,
	Carl Love <carll@us.ibm.com>
Subject: Re: re-enable Nehalem raw Offcore-Events support
Date: Sun, 1 May 2011 20:00:38 +0200	[thread overview]
Message-ID: <20110501180038.GB27830@elte.hu> (raw)
In-Reply-To: <20110501044551.GB16177@alboin.amr.corp.intel.com>


* Andi Kleen <ak@linux.intel.com> wrote:

> > I would say that most if not all of the events are not generalizable
> > in the sense that you are talking about; the events are very
> > specific to the Torrent chip.  For example, the Torrent chip
> 
> It's similar also on Intel chips. [...]

You seem to be seriously misinformed about Intel CPUs.

There are a fair number of events on Intel CPUs that can be generalized and 
which we have already generalized. Here's a selection:

 Performance counter stats for './fill_1b':

       2829.562519 task-clock               #    0.994 CPUs utilized          
                27 context-switches         #    0.000 M/sec                  
                52 CPU-migrations           #    0.000 M/sec                  
                99 page-faults              #    0.000 M/sec                  
     8,559,062,611 cycles                   #    3.025 GHz                      (20.02%)
     2,530,761,381 stalled-cycles-frontend  #   29.57% frontend cycles idle     (30.03%)
       423,070,037 stalled-cycles-backend   #    4.94% backend  cycles idle     (40.04%)
    18,043,436,126 instructions             #    2.11  insns per cycle        
                                            #    0.14  stalled cycles per insn  (50.04%)
     1,007,704,770 branches                 #  356.134 M/sec                    (60.04%)
           521,894 branch-misses            #    0.05% of all branches          (60.02%)
         9,424,849 L1-dcache-loads          #    3.331 M/sec                    (50.03%)
         1,028,884 L1-dcache-load-misses    #   10.92% of all L1-dcache hits    (50.02%)
           490,266 LLC-loads                #    0.173 M/sec                    (39.99%)
           133,226 LLC-load-misses          #    0.047 M/sec                    (10.01%)

        2.846836822  seconds time elapsed

Thanks,

	Ingo

  reply	other threads:[~2011-05-01 18:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 15:04 Vince Weaver
2011-04-29 15:27 ` Andi Kleen
2011-04-29 16:49   ` Ingo Molnar
2011-04-29 16:42 ` Ingo Molnar
2011-04-29 18:01   ` Vince Weaver
2011-04-29 18:57     ` Ingo Molnar
2011-04-30  2:17       ` Vince Weaver
2011-04-30  7:14         ` Pekka Enberg
2011-04-30 20:47           ` Vince Weaver
2011-05-01 18:31             ` Ingo Molnar
2011-04-30  8:11         ` Borislav Petkov
2011-04-30 21:03           ` Vince Weaver
2011-05-09 11:01       ` stephane eranian
2011-05-10  9:35         ` Ingo Molnar
2011-04-29 22:16   ` Borislav Petkov
2011-04-30  1:49     ` Vince Weaver
2011-04-30  1:53   ` Vince Weaver
2011-04-30 20:58     ` Vince Weaver
2011-04-30 21:09       ` Alan Cox
2011-04-29 17:17 ` Pekka Enberg
2011-04-29 17:25   ` Andi Kleen
2011-04-29 17:37     ` Pekka Enberg
2011-04-29 17:46       ` Vince Weaver
2011-04-29 17:59         ` Pekka Enberg
2011-04-29 17:42     ` Thomas Gleixner
2011-04-30 20:06       ` Corey Ashford
2011-05-01  4:45         ` Andi Kleen
2011-05-01 18:00           ` Ingo Molnar [this message]
2011-05-01 17:55         ` Ingo Molnar
2011-05-02 18:32           ` Corey Ashford

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=20110501180038.GB27830@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@linux.intel.com \
    --cc=carll@us.ibm.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=eranian@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vweaver1@eecs.utk.edu \
    /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®