From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
James Clark <james.clark@linaro.org>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
Clark Williams <williams@redhat.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 0/6 v2] Fixups for kernel maps insertion
Date: Fri, 28 Feb 2025 16:03:48 -0800 [thread overview]
Message-ID: <Z8JO5Jp2b4OyHImx@google.com> (raw)
In-Reply-To: <20250228211734.33781-1-acme@kernel.org>
On Fri, Feb 28, 2025 at 06:17:28PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> Hi Namhyung,
>
> Here are the patches from the recent session on fixing the build
> when DEBUG=1 is used, please take a look.
Looks good. It's more fine-grained than I expected. :)
>
> I think that since there are no reported problems and ended up
> being a sizeable series, we better apply it to perf-tools-next,
Sure, will add there.
Thanks,
Namhyung
>
> Best Regards,
>
> - Arnaldo
>
> v2: Use map__set_kmap_maps() as suggested by Ian.
>
> Arnaldo Carvalho de Melo (3):
> perf maps: Introduce map__set_kmap_maps() for kernel maps
> perf maps: Set the kmaps for newly created/added kernel maps
> perf maps: Add missing map__set_kmap_maps() when replacing a kernel map
>
> Namhyung Kim (3):
> perf machine: Fixup kernel maps ends after adding extra maps
> perf maps: Fixup maps_by_name when modifying maps_by_address
> perf machine: Fix insertion of PERF_RECORD_KSYMBOL related kernel maps
>
> tools/perf/util/machine.c | 6 ++--
> tools/perf/util/maps.c | 58 +++++++++++++++++++++++++++++++++------
> 2 files changed, 52 insertions(+), 12 deletions(-)
>
> --
> 2.48.1
>
next prev parent reply other threads:[~2025-03-01 0:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 21:17 [PATCH 0/6 v2] Fixups for kernel maps insertion Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 1/6] perf maps: Introduce map__set_kmap_maps() for kernel maps Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 2/6] perf maps: Set the kmaps for newly created/added " Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 3/6] perf machine: Fixup kernel maps ends after adding extra maps Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 4/6] perf maps: Fixup maps_by_name when modifying maps_by_address Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 5/6] perf maps: Add missing map__set_kmap_maps() when replacing a kernel map Arnaldo Carvalho de Melo
2025-02-28 21:17 ` [PATCH 6/6] perf machine: Fix insertion of PERF_RECORD_KSYMBOL related kernel maps Arnaldo Carvalho de Melo
2025-03-01 0:03 ` Namhyung Kim [this message]
2025-03-03 20:45 ` [PATCH 0/6 v2] Fixups for kernel maps insertion Namhyung Kim
2025-03-05 22:55 ` Ian Rogers
2025-03-06 17:14 ` 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=Z8JO5Jp2b4OyHImx@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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.