linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Petlan <mpetlan@redhat.com>
To: Christian Neugebauer <christian.neugebauer@smail.inf.h-brs.de>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Haswell EP some uncore imc counter are missing
Date: Wed, 21 Sep 2016 14:07:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LRH.2.20.1609211355400.10180@Diego> (raw)
In-Reply-To: <20160917180155.Horde.5aCQxGa9_V0-tbqDKZDTDx2@horde.inf.h-brs.de>

On Sat, 17 Sep 2016, Christian Neugebauer wrote:
>
> Hi,
>
> We encountered the following problem with perf. We want to measure the total 
> memory bandwidth by using the uncore imc counter uncore_imc_0, uncore_imc_1, 
> ..., uncore_imc_7. In our system the counter uncore_imc_2, uncore_imc_3, 
> uncore_imc_6, uncore_imc_7 are NOT listed under /sys/devices. Only 
> uncore_imc_0, uncore_imc_1, uncore_imc_4, uncore_imc_5 are available (linked 
> under /sys/device and accessible via perf).
>

Hi,

When I tested uncore with perf on (probably) the same (or very similar) Haswell
EP CPU as the one of yours, I also have seen only imcs 0, 1, 4, 5. Are you sure
the 2, 3, 6, 7 should really be there (are supported by the CPU itself)?

My guess would be that the 2, 3, 6, 7 slots are reserved/unused.

Could you attach more info about your CPU topology (cpuid, lstopo, ...)?

This was the CPU I used:

Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz
Family: 6
Model: 63
Stepping: 2
RAM: 31976 MB
56 processors on 28 cores organized into 2 numa nodes

Unfortunatelly, I didn't stored my topology logs, however I think it is as I
said above.

Cheers,
Michael


> Our setup:
>
> - 2 x Intel Xeon E5-2697 v3 (Haswell EP)
> - uname -a
> Linux wr5 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 11:15:56 CDT 2016 
> x86_64 x86_64 x86_64 GNU/Linux
> - perf --version
> perf version 2.6.32-642.4.2.el6.x86_64.debug
>
> From my understanding 8 imc counter in total should be available for Haswell 
> EP. The kernel is a fresh build which seems to have all latest perf changes 
> in it. I also checked the perf source code briefly. I could do more debugging 
> and try to find out the problem but before that I want to know if this is 
> either a known problem, an unknown problem or no problem at all because there 
> are restrictions that I'm not aware of.
>
> I also double checked other machines (same kernel though). E.g Intel Xeon 
> E5-2697 v2 (Ivy Bridge EP) shows me 8 counters as expected, and if I remember 
> correctly Intel Xeon EP E5-2670 (Sandy Bridge EP) had 4 counter, could double 
> check that if necessary.
>
> Chris
> -- 
> Christian Neugebauer
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" 
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  reply	other threads:[~2016-09-21 12:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-17 16:01 Haswell EP some uncore imc counter are missing Christian Neugebauer
2016-09-21 12:07 ` Michael Petlan [this message]
2016-09-21 20:16   ` Liang, Kan
2016-09-27 22:20     ` Christian Neugebauer

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=alpine.LRH.2.20.1609211355400.10180@Diego \
    --to=mpetlan@redhat.com \
    --cc=christian.neugebauer@smail.inf.h-brs.de \
    --cc=linux-perf-users@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).