mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: peterz@infradead.org, acme@kernel.org
Cc: linux-kernel@vger.kernel.org, jolsa@kernel.org, eranian@google.com
Subject: Fix Skylake PEBS data source for perf
Date: Wed,  7 Jun 2017 16:22:22 -0700	[thread overview]
Message-ID: <20170607232226.26365-1-andi@firstfloor.org> (raw)

Fix data source reporting for Skylake and Skylake Server.
The encodings have changed to express support for L4 and persistent
memory. 

The first patch is a (independent) cleanup.

The second is for the kernel and the third for perf/tools.
The kernel part and perf tools will compile independently.

v1:
Initial post
v2:
Merged some patches.
Change encoding to use special bit for each combination instead
of modifiers.

             reply	other threads:[~2017-06-07 23:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 23:22 Andi Kleen [this message]
2017-06-07 23:22 ` [PATCH v2 1/4] perf/x86: Move Nehalem PEBS code to flag Andi Kleen
2017-06-07 23:22 ` [PATCH v2 2/4] perf/x86: Fix data source decoding for Skylake Andi Kleen
2017-06-08  8:15   ` Peter Zijlstra
2017-06-08 19:40     ` Stephane Eranian
2017-06-08 20:03       ` Peter Zijlstra
2017-06-09 16:47         ` Andi Kleen
2017-06-08 20:10       ` Andi Kleen
2017-06-08 20:22         ` Peter Zijlstra
2017-06-09  8:04     ` Madhavan Srinivasan
2017-06-07 23:22 ` [PATCH v2 3/4] perf, tools: Add support for printing new mem_info encodings Andi Kleen
2017-06-07 23:22 ` [PATCH v2 4/4] perf, tools: Add test cases for new data source encoding Andi Kleen
2017-06-09  0:13 Fix Skylake PEBS data source for perf Andi Kleen
2017-06-22  0:03 Andi Kleen
2017-06-22 12:38 ` Thomas Gleixner

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=20170607232226.26365-1-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.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