mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: peterz@infradead.org, acme@kernel.org,
	linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 2/4] perf/x86: Fix data source decoding for Skylake
Date: Mon, 3 Jul 2017 12:38:41 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1707031236300.2188@nanos> (raw)
In-Reply-To: <20170622000304.27918-3-andi@firstfloor.org>

On Wed, 21 Jun 2017, Andi Kleen wrote:
> I didn't add a generic flag for hops because it's not needed
> for Skylake.

When is that going to come? 

> diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
> index b1c0b187acfe..7cfeb54e0b5a 100644
> --- a/include/uapi/linux/perf_event.h
> +++ b/include/uapi/linux/perf_event.h
> @@ -931,14 +931,20 @@ union perf_mem_data_src {
>  			mem_snoop:5,	/* snoop mode */
>  			mem_lock:2,	/* lock instr */
>  			mem_dtlb:7,	/* tlb access */
> -			mem_rsvd:31;
> +			mem_lvl_num:4,	/* memory hierarchy level number */
> +			mem_remote:1,   /* remote */
> +			mem_snoopx:2,	/* snoop mode, ext */

Is that extending snoopx another time?

The question really is, whether the 2 bits are going to be sufficient for a
while or are we going to add snoopx2 in a few month from now.

Thanks,

	tglx

  reply	other threads:[~2017-07-03 10:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22  0:03 Fix Skylake PEBS data source for perf Andi Kleen
2017-06-22  0:03 ` [PATCH 1/4] perf/x86: Move Nehalem PEBS code to flag Andi Kleen
2017-06-22  0:03 ` [PATCH 2/4] perf/x86: Fix data source decoding for Skylake Andi Kleen
2017-07-03 10:38   ` Thomas Gleixner [this message]
2017-06-22  0:03 ` [PATCH 3/4] perf, tools: Add support for printing new mem_info encodings Andi Kleen
2017-06-22  0:03 ` [PATCH 4/4] perf, tools: Add test cases for new data source encoding Andi Kleen
2017-06-22 12:38 ` Fix Skylake PEBS data source for perf 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=alpine.DEB.2.20.1707031236300.2188@nanos \
    --to=tglx@linutronix.de \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.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

all inboxes | Powered by JetHome®