From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users <linux-perf-users@vger.kernel.org>
Subject: Re: [BUG] perf kmem: Broken because of missing tracepoints
Date: Thu, 5 Jan 2023 13:27:30 -0300 [thread overview]
Message-ID: <Y7b6cmRE/+5HJLCa@kernel.org> (raw)
In-Reply-To: <b5f82509-41d7-7598-6ec2-fcfa74c7ddaa@amd.com>
Em Thu, Jan 05, 2023 at 07:03:25PM +0530, Ravi Bangoria escreveu:
> Hello,
>
> Two tracepoints, kmem:kmalloc_node and kmem:kmem_cache_alloc_node used by perf-
> kmem tool were removed from kernel by commit 11e9734bcb6a7 ("mm/slab_common:
> unify NUMA and UMA version of tracepoints"). This causes issue while running
> perf kmem on latest kernel:
>
> $ sudo ./perf kmem record
> event syntax error: 'kmem:kmalloc_node'
> \___ unknown tracepoint
>
> $ sudo ./perf kmem record
> event syntax error: 'kmem:kmem_cache_alloc_node'
> \___ unknown tracepoint
>
> Haven't got a chance to debug further. Anyone aware of this?
I didn't notice this so far, would be good to have a fix soon.
Thanks,
- Arnaldo
next prev parent reply other threads:[~2023-01-05 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 13:33 [BUG] perf kmem: Broken because of missing tracepoints Ravi Bangoria
2023-01-05 16:27 ` Arnaldo Carvalho de Melo [this message]
2023-01-06 5:22 ` Leo Yan
2023-01-06 13:04 ` Ravi Bangoria
2023-01-06 17:27 ` Arnaldo Carvalho de Melo
2023-01-06 17:44 ` Arnaldo Carvalho de Melo
2023-01-07 4:13 ` Leo Yan
2023-01-07 18:41 ` Vlastimil Babka
2023-01-08 6:30 ` Leo Yan
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=Y7b6cmRE/+5HJLCa@kernel.org \
--to=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.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).