All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
Cc: Thomas Falcon <thomas.falcon@intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	James Clark <james.clark@linaro.org>
Subject: Re: [PATCH v2 2/6] perf mem: Add support for printing PERF_MEM_LVLNUM_L0
Date: Fri, 31 Jul 2026 14:37:06 -0700	[thread overview]
Message-ID: <am0Vgnayr0WVdeOH@google.com> (raw)
In-Reply-To: <8829286c-c05c-456d-82ad-6e75ab864f1d@linux.intel.com>

On Thu, Jul 30, 2026 at 01:46:27PM +0800, Mi, Dapeng wrote:
> 
> On 7/29/2026 1:13 AM, Namhyung Kim wrote:
> > Hello,
> >
> > On Mon, Jul 13, 2026 at 07:43:55PM -0500, Thomas Falcon wrote:
> >> From: Dapeng Mi <dapeng1.mi@linux.intel.com>
> >>
> >> Add support for printing PERF_MEM_LVLNUM_L0 in perf mem report.
> > What's the L0, by the way?
> 
> Per my understanding, the L0 cache is newly added a small piece of cache
> which is the closest, lowest-latency memory cache tied directly to the
> execution pipeline. 
> 
> The table "Table 9-4. Data Source Field Encodings for Panther Cove and
> Coyote Cove Microarchitectures" in the ISE doc chapter "9.2.1 Panther Cove
> and Coyote Cove Microarchitectures Memory Auxiliary Field Layout" indicates
> the code "01H" means the "L0 Hit - Minimal latency core cache hit. This
> request was satisfied by the L0 data cache."
> 
> https://www.intel.com/content/www/us/en/content-details/922690/intel-architecture-instruction-set-extensions-programming-reference.html 

Interesting, thanks for the explanation!

Thanks,
Namhyung


  reply	other threads:[~2026-07-31 21:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  0:43 [PATCH v2 0/6] perf: Add support for memory region/range reporting Thomas Falcon
2026-07-14  0:43 ` [PATCH v2 1/6] perf mem: Fix size tracking for mem_lvl's in perf_script__meminfo_scnprintf() Thomas Falcon
2026-07-14  0:51   ` sashiko-bot
2026-07-27 17:06     ` Falcon, Thomas
2026-07-15  6:59   ` Mi, Dapeng
2026-07-14  0:43 ` [PATCH v2 2/6] perf mem: Add support for printing PERF_MEM_LVLNUM_L0 Thomas Falcon
2026-07-15  7:11   ` Mi, Dapeng
2026-07-28 17:13   ` Namhyung Kim
2026-07-30  5:46     ` Mi, Dapeng
2026-07-31 21:37       ` Namhyung Kim [this message]
2026-07-14  0:43 ` [PATCH v2 3/6] perf tools: Show memory region in perf-c2c subcommand Thomas Falcon
2026-07-14  0:56   ` sashiko-bot
2026-07-27 16:37     ` Falcon, Thomas
2026-07-28 17:17   ` Namhyung Kim
2026-07-30  5:50     ` Mi, Dapeng
2026-07-14  0:43 ` [PATCH v2 4/6] perf tools: Show memory region in perf-script subcommand Thomas Falcon
2026-07-14  0:59   ` sashiko-bot
2026-07-28 17:18   ` Namhyung Kim
2026-07-30  5:50     ` Mi, Dapeng
2026-07-14  0:43 ` [PATCH v2 5/6] perf header: Support memory ranges Thomas Falcon
2026-07-28 17:33   ` Namhyung Kim
2026-07-28 21:33     ` Falcon, Thomas
2026-07-31 21:38       ` Namhyung Kim
2026-07-14  0:43 ` [PATCH v2 6/6] perf c2c: print memory region data with stdio output Thomas Falcon
2026-07-14  0:57   ` sashiko-bot
2026-07-27 17:05     ` Falcon, Thomas
2026-07-28 17:34   ` Namhyung Kim

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=am0Vgnayr0WVdeOH@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dapeng1.mi@linux.intel.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=thomas.falcon@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.