From: Ravi Bangoria <ravi.bangoria@amd.com>
To: arnaldo.melo@gmail.com, acme@redhat.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>,
Ravi Bangoria <ravi.bangoria@amd.com>
Subject: Re: [PATCH 1/1 FYI] tools headers UAPI: Sync linux/perf_event.h with the kernel sources
Date: Wed, 26 Oct 2022 08:54:55 +0530 [thread overview]
Message-ID: <e61eeed0-0b93-4bac-6247-55fabb70eb87@amd.com> (raw)
In-Reply-To: <Y1hBY+51vpyERSrZ@kernel.org>
Hi Arnaldo,
On 26-Oct-22 1:34 AM, arnaldo.melo@gmail.com wrote:
> To pick the changes in:
>
> cfef80bad4cf79cd ("perf/uapi: Define PERF_MEM_SNOOPX_PEER in kernel header file")
> ee3e88dfec23153d ("perf/mem: Introduce PERF_MEM_LVLNUM_{EXTN_MEM|IO}")
> b4e12b2d70fd9ecc ("perf: Kill __PERF_SAMPLE_CALLCHAIN_EARLY")
>
> A previous sync:
>
> b7ddd38ccc723f0d ("tools headers UAPI: Sync include/uapi/linux/perf_event.h header with the kernel")
>
> brought a PERF_MEM_LVLNUM_CXL, and used it in
> tools/perf/util/mem-events.c, but when the feature really hit the kernel
> that define had been renamed to PERF_MEM_LVLNUM_EXTN_MEM, so reflect
> that on the tooling side.
It's other way around. I proposed PERF_MEM_LVLNUM_EXTN_MEM but it was
vague and thus we replaced it with PERF_MEM_LVLNUM_CXL. So tool side
file is correct and kernel header needs to be fixed:
https://lore.kernel.org/lkml/f6268268-b4e9-9ed6-0453-65792644d953@amd.com
Thanks,
Ravi
next prev parent reply other threads:[~2022-10-26 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:04 [PATCH 1/1 FYI] tools headers UAPI: Sync linux/perf_event.h with the kernel sources arnaldo.melo
2022-10-26 3:24 ` Ravi Bangoria [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 20:21 [PATCH 1/1 fyi] " arnaldo.melo
2022-10-26 13:45 [PATCH 1/1 FYI] " arnaldo.melo
2022-02-01 15:18 [PATCH 1/1 fyi] " Arnaldo Carvalho de Melo
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=e61eeed0-0b93-4bac-6247-55fabb70eb87@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=arnaldo.melo@gmail.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).