linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Ian Rogers <irogers@google.com>, Jiri Olsa <jolsa@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: perf amd: PERF_MEM_LVLNUM_CXL -> PERF_MEM_LVLNUM_EXTN_MEM
Date: Tue, 25 Oct 2022 16:55:11 -0300	[thread overview]
Message-ID: <Y1g/H2/ljZ1rGmM9@kernel.org> (raw)

Ravi,

	I'm updating the tools header copies and noticed that a previous
sync brought PERF_MEM_LVLNUM_CXL but now this got renamed to
PERF_MEM_LVLNUM_EXTN_MEM, so I had to add this change to the sync of
tools/uapi/linux/perf_event.h, please ack.

Thanks,

- Arnaldo

⬢[acme@toolbox perf-urgent]$ git diff tools/perf/util/mem-events.c
diff --git a/tools/perf/util/mem-events.c b/tools/perf/util/mem-events.c
index b3a91093069a5715..c80fce18025051ae 100644
--- a/tools/perf/util/mem-events.c
+++ b/tools/perf/util/mem-events.c
@@ -295,7 +295,7 @@ static const char * const mem_lvl[] = {
 };

 static const char * const mem_lvlnum[] = {
-       [PERF_MEM_LVLNUM_CXL] = "CXL",
+       [PERF_MEM_LVLNUM_EXTN_MEM] = "Extension mem",
        [PERF_MEM_LVLNUM_IO] = "I/O",
        [PERF_MEM_LVLNUM_ANY_CACHE] = "Any cache",
        [PERF_MEM_LVLNUM_LFB] = "LFB/MAB",
⬢[acme@toolbox perf-urgent]$

-- 

- Arnaldo

             reply	other threads:[~2022-10-25 19:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 19:55 Arnaldo Carvalho de Melo [this message]
2022-10-26  5:46 ` perf amd: PERF_MEM_LVLNUM_CXL -> PERF_MEM_LVLNUM_EXTN_MEM Ravi Bangoria
2022-10-26 13:40   ` Arnaldo Carvalho de Melo
2022-10-26 13:52     ` Ravi Bangoria

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=Y1g/H2/ljZ1rGmM9@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.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 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).