From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf report: Add 'tgid' sort key
Date: Wed, 26 Feb 2025 18:40:25 -0300 [thread overview]
Message-ID: <Z7-KSRttQLImuWtJ@x1> (raw)
In-Reply-To: <Z7-J5vHqHF4kc1HB@x1>
On Wed, Feb 26, 2025 at 06:38:50PM -0300, Arnaldo Carvalho de Melo wrote:
> On Wed, Feb 26, 2025 at 06:38:00PM -0300, Arnaldo Carvalho de Melo wrote:
> > On Wed, Feb 26, 2025 at 11:34:13AM -0800, Namhyung Kim wrote:
> > > On Tue, Feb 25, 2025 at 08:48:56PM +0100, Arnaldo Carvalho de Melo wrote:
> > > > On Tue, Feb 25, 2025 at 08:25:35PM +0100, Arnaldo Carvalho de Melo wrote:
> > > > > On Tue, Feb 25, 2025 at 08:11:17PM +0100, Arnaldo Carvalho de Melo wrote:
> > > > > > On Tue, Feb 25, 2025 at 08:07:18PM +0100, Arnaldo Carvalho de Melo wrote:
> > > > > > > On Mon, Feb 24, 2025 at 11:51:35PM -0800, Namhyung Kim wrote:
> > > > > > > > On Mon, Feb 24, 2025 at 08:40:37PM -0800, Ian Rogers wrote:
> > > > > > > > > On Mon, Feb 24, 2025 at 6:51 PM Namhyung Kim <namhyung@kernel.org> wrote:
> > > > > > > > > > On Mon, Feb 24, 2025 at 10:18:37AM -0800, Ian Rogers wrote:
> > > > > > > > [SNIP]
> > > > > > > > > > > I thought the real-time processing had to use
> > > > > > > > > > > maps__fixup_overlap_and_insert (rather than maps__insert) as mmap
> > > > > > > > > > > events only give us VMA data and two mmaps may have been merged.
> > > > > > > > > > > Shouldn't doing this change be the simplest fix?
> > > > > >
> > > > > > > > > > Make sense. How about this?
> > > > > >
> > > > > > > > > Lgtm, I have no way to test the issue. Why does maps__fixup_end need
> > > > > > > > > to get pushed later?
> > > > > >
> > > > > > > > I just noticed it would add extra kernel maps after modules. I think it
> > > > > > > > should fixup end address of the kernel maps after adding all maps first.
> > > > > >
> > > > > > > > Arnaldo, can you please test this?
> > > > > >
> > > > > > > Trying it now.
> > > > > >
> > > > > > Now we have something different:
> > > > > >
> > > > > > root@number:~# perf record sleep
> > > > > > sleep: missing operand
> > > > > > Try 'sleep --help' for more information.
> > > > > > [ perf record: Woken up 1 times to write data ]
> > > > > > perf: util/maps.c:80: check_invariants: Assertion `RC_CHK_EQUAL(map__kmap(map)->kmaps, maps)' failed.
> > > > > > Aborted (core dumped)
> > > > > > root@number:~#
> > > > >
> > > > > __maps__insert() does:
> > > > >
> > > > > if (dso && dso__kernel(dso)) {
> > > > > struct kmap *kmap = map__kmap(new);
> > > > >
> > > > > if (kmap)
> > > > > kmap->kmaps = maps;
> > > > > else
> > > > > pr_err("Internal error: kernel dso with non kernel map\n");
> > > > > }
> > > > >
> > > > > while maps__fixup_overlap_and_insert() doesn't.
> > > > >
> > > > > It calls __maps__insert_sorted() that probably should do what
> > > > > __maps__insert() does?
> > > >
> > > > Ok, so I did the following patch but this case fails:
> > > >
> > > > @@ -910,6 +928,7 @@ static int __maps__fixup_overlap_and_insert(struct maps *maps, struct map *new)
> > > > */
> > > > map__put(maps_by_address[i]);
> > > > maps_by_address[i] = map__get(new);
> > > > + map__set_kmap(new, maps);
> > > > check_invariants(maps);
> > > > return err;
> > > > }
> > > >
> > > > With:
> > > >
> > > > perf: util/maps.c:110: check_invariants: Assertion `refcount_read(map__refcnt(map)) > 1' failed.
> > > >
> > > > As:
> > > >
> > > > 106 /*
> > > > 107 * Maps by name maps should be in maps_by_address, so
> > > > 108 * the reference count should be higher.
> > > > 109 */
> > > > 110 assert(refcount_read(map__refcnt(map)) > 1);
> > > >
> > > > Since it is just replacing the map in the maps_by_address and not
> > > > touching on the maps_by_name? Thus the refcount is just 1:
> > >
> > > Sounds like it. Can you add this on top?
> >
> > Trying, but somehow its not applying cleanly, checking:
> >
> > ⬢ [acme@toolbox perf-tools]$ patch -p1 < ~/wb/1.patch
> > patching file tools/perf/util/maps.c
> > Hunk #1 succeeded at 815 (offset 18 lines).
> > Hunk #2 succeeded at 826 (offset 18 lines).
> > Hunk #3 succeeded at 846 (offset 18 lines).
> > Hunk #4 succeeded at 893 (offset 18 lines).
> > Hunk #5 succeeded at 919 (offset 18 lines).
> > Hunk #6 FAILED at 923.
> > 1 out of 6 hunks FAILED -- saving rejects to file tools/perf/util/maps.c.rej
> > ⬢ [acme@toolbox perf-tools]$
> >
> > ⬢ [acme@toolbox perf-tools]$ git log --oneline -5
> > 4a9f5d76130b707f (HEAD -> perf-tools) wip: acme
> > d5ba0f5af35937c7 wip: namhyung
> > 42367eca7604e16e (perf-tools/tmp.perf-tools, perf-tools/perf-tools) tools: Remove redundant quiet setup
> > 293f324ce96d7001 tools: Unify top-level quiet infrastructure
> > 9fae5884bb0e3480 (tag: perf-tools-fixes-for-v6.14-2025-01-30) perf cpumap: Fix die and cluster IDs
> > ⬢ [acme@toolbox perf-tools]$
>
> ⬢ [acme@toolbox perf-tools]$ cat tools/perf/util/maps.c.rej
> --- tools/perf/util/maps.c
> +++ tools/perf/util/maps.c
> @@ -923,6 +936,10 @@ static int __maps__fixup_overlap_and_insert(struct maps *maps, struct map *new)
> */
> map__put(maps_by_address[i]);
> maps_by_address[i] = map__get(new);
> + if (maps_by_name) {
> + map__put(maps_by_name[ni]);
> + maps_by_name[ni] = map__get(new);
> + }
> check_invariants(maps);
> return err;
> }
> ⬢ [acme@toolbox perf-tools]$
>
> Fixing this up by hand
I see, I had tried this after sending that patch:
map__set_kmap(new, maps);
Before check_invariants(), but that doesn't make sense, I should've
dropped that, doing it now.
- Arnaldo
next prev parent reply other threads:[~2025-02-26 21:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 0:01 [PATCH] perf report: Add 'tgid' sort key Namhyung Kim
2025-02-11 22:43 ` Ian Rogers
2025-02-12 21:05 ` Arnaldo Carvalho de Melo
2025-02-12 21:07 ` Arnaldo Carvalho de Melo
2025-02-12 21:59 ` Ian Rogers
2025-02-12 22:10 ` Ian Rogers
2025-02-13 1:52 ` Namhyung Kim
2025-02-14 22:22 ` Arnaldo Carvalho de Melo
2025-02-18 20:36 ` Arnaldo Carvalho de Melo
2025-02-18 21:01 ` Arnaldo Carvalho de Melo
2025-02-18 22:03 ` Namhyung Kim
2025-02-19 14:37 ` Arnaldo Carvalho de Melo
2025-02-19 14:47 ` Arnaldo Carvalho de Melo
2025-02-19 21:10 ` Namhyung Kim
2025-02-20 17:12 ` Ian Rogers
2025-02-21 7:04 ` Namhyung Kim
2025-02-24 18:18 ` Ian Rogers
2025-02-25 2:51 ` Namhyung Kim
2025-02-25 4:40 ` Ian Rogers
2025-02-25 7:51 ` Namhyung Kim
2025-02-25 19:07 ` Arnaldo Carvalho de Melo
2025-02-25 19:11 ` Arnaldo Carvalho de Melo
2025-02-25 19:25 ` Arnaldo Carvalho de Melo
2025-02-25 19:48 ` Arnaldo Carvalho de Melo
2025-02-26 19:34 ` Namhyung Kim
2025-02-26 21:37 ` Arnaldo Carvalho de Melo
2025-02-26 21:38 ` Arnaldo Carvalho de Melo
2025-02-26 21:40 ` Arnaldo Carvalho de Melo [this message]
2025-02-26 21:49 ` Arnaldo Carvalho de Melo
2025-02-26 22:17 ` 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=Z7-KSRttQLImuWtJ@x1 \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@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).