From: Andi Kleen <ak@linux.intel.com>
To: Juan <genomeme@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
jolsa@redhat.com, alexander.shishkin@linux.intel.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Perf JSON events mismatch with Intel SDM
Date: Sun, 15 Jul 2018 20:59:08 -0700 [thread overview]
Message-ID: <20180716035908.GA25412@tassilo.jf.intel.com> (raw)
In-Reply-To: <CA+eKabDFV0UZ_52jbamj+=cGdD7OSRHMhuFHbni1SkBzRrd57g@mail.gmail.com>
> now need to dive in deep into the actual implementation. Simple question: is this a bug?
These are derived events from MEM_TRANS_RETIRED.LOAD_LATENCY, which is in
the SDM. It's not a bug. In general the event lists used by perf are
newer versions than what is in the SDM.
-Andi
next parent reply other threads:[~2018-07-16 3:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+eKabDFV0UZ_52jbamj+=cGdD7OSRHMhuFHbni1SkBzRrd57g@mail.gmail.com>
2018-07-16 3:59 ` Andi Kleen [this message]
[not found] ` <CA+eKabDaAVFR-eeXDaocQQWT=82XouV8fw3zcJ9cos=O7v1W3g@mail.gmail.com>
2018-07-16 15:37 ` Andi Kleen
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=20180716035908.GA25412@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=genomeme@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome