From: Peter Zijlstra <peterz@infradead.org>
To: Artem Savkov <asavkov@redhat.com>
Cc: linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] perf tools: annotation browser from c2c tui
Date: Thu, 8 Jun 2023 15:25:33 +0200 [thread overview]
Message-ID: <20230608132533.GL998233@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230608084407.140323-1-asavkov@redhat.com>
On Thu, Jun 08, 2023 at 10:44:05AM +0200, Artem Savkov wrote:
> These patches add ability to start annotation browser from c2c report
> tui. The idea comes from Arnaldo's "Profiling Data Structures" talk [1].
>
> [1]: http://vger.kernel.org/~acme/prez/linux-plumbers-2022/
So what are the plans for doing IP to datatype::member resolution and
deleting this C2C abomination?
/me still regretting ever letting c2c happen..
next prev parent reply other threads:[~2023-06-08 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 8:44 [PATCH v2 0/2] perf tools: annotation browser from c2c tui Artem Savkov
2023-06-08 8:44 ` [PATCH v2 1/2] perf util: move symbol__new_unresolved() to util/symbol.c Artem Savkov
2023-06-08 8:44 ` [PATCH v2 2/2] perf tools: allow running annotation browser from c2c-report Artem Savkov
2023-06-08 13:25 ` Peter Zijlstra [this message]
2023-06-08 17:28 ` [PATCH v2 0/2] perf tools: annotation browser from c2c tui Namhyung Kim
2023-06-08 21:09 ` Namhyung Kim
2023-06-09 8:37 ` Artem Savkov
2023-06-14 18:38 ` Arnaldo Carvalho de Melo
2023-06-14 18:40 ` Arnaldo Carvalho de Melo
2023-06-19 7:15 ` Artem Savkov
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=20230608132533.GL998233@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=asavkov@redhat.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.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).