From: Namhyung Kim <namhyung@kernel.org>
To: Song Liu <song@kernel.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Ian Rogers <irogers@google.com>,
James Clark <james.clark@arm.com>,
Changbin Du <changbin.du@huawei.com>,
linux-perf-users@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>,
Liam Howlett <liam.howlett@oracle.com>,
Ingo Molnar <mingo@redhat.com>, Artem Savkov <asavkov@redhat.com>,
Leo Yan <leo.yan@linaro.org>,
bpf@vger.kernel.org, Athira Rajeev <atrajeev@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Vincent Whitchurch <vincent.whitchurch@axis.com>,
Colin Ian King <colin.i.king@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 0/6] maps memory improvements and fixes
Date: Tue, 13 Feb 2024 10:09:28 -0800 [thread overview]
Message-ID: <170784747634.4188477.9115348718072311064.b4-ty@kernel.org> (raw)
In-Reply-To: <20240210031746.4057262-1-irogers@google.com>
On Fri, 9 Feb 2024 19:17:40 -0800, Ian Rogers wrote:
> First 6 patches from:
> https://lore.kernel.org/lkml/20240202061532.1939474-1-irogers@google.com/
>
> v3. Fix latent concurrent modification bug in maps__for_each_map.
> v2. Fix NO_LIBUNWIND=1 build issue.
>
> Ian Rogers (6):
> perf maps: Switch from rbtree to lazily sorted array for addresses
> perf maps: Get map before returning in maps__find
> perf maps: Get map before returning in maps__find_by_name
> perf maps: Get map before returning in maps__find_next_entry
> perf maps: Hide maps internals
> perf maps: Locking tidy up of nr_maps
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
--
Namhyung Kim <namhyung@kernel.org>
prev parent reply other threads:[~2024-02-13 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 3:17 Ian Rogers
2024-02-10 3:17 ` [PATCH v3 1/6] perf maps: Switch from rbtree to lazily sorted array for addresses Ian Rogers
2024-02-12 20:15 ` Namhyung Kim
2024-02-12 20:19 ` Ian Rogers
2024-02-12 20:26 ` Namhyung Kim
2024-02-12 20:37 ` Ian Rogers
2024-02-10 3:17 ` [PATCH v3 2/6] perf maps: Get map before returning in maps__find Ian Rogers
2024-02-10 3:17 ` [PATCH v3 3/6] perf maps: Get map before returning in maps__find_by_name Ian Rogers
2024-02-10 3:17 ` [PATCH v3 4/6] perf maps: Get map before returning in maps__find_next_entry Ian Rogers
2024-02-10 3:17 ` [PATCH v3 5/6] perf maps: Hide maps internals Ian Rogers
2024-02-10 3:17 ` [PATCH v3 6/6] perf maps: Locking tidy up of nr_maps Ian Rogers
2024-02-13 18:09 ` Namhyung Kim [this message]
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=170784747634.4188477.9115348718072311064.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adobriyan@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asavkov@redhat.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=changbin.du@huawei.com \
--cc=colin.i.king@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=kprateek.nayak@amd.com \
--cc=leo.yan@linaro.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=song@kernel.org \
--cc=vincent.whitchurch@axis.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
all inboxes | Powered by JetHome®