[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYSg7EO0j4y2z5LB@kernel.org>
Date: Thu, 21 Dec 2023 17:32:44 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Ingo Molnar <mingo@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Stephane Eranian <eranian@...gle.com>,
Masami Hiramatsu <mhiramat@...nel.org>,
Andi Kleen <ak@...ux.intel.com>, linux-trace-devel@...r.kernel.org,
linux-toolchains@...r.kernel.org
Subject: Re: [PATCH 13/52] perf annotate-data: Add dso->data_types tree
Em Thu, Dec 21, 2023 at 05:13:11PM -0300, Arnaldo Carvalho de Melo escreveu:
> > At some point we need to make these feature specific members to be
> > associated on demand, maybe thru some hash table, etc.
> > I.e. the most basic workflow, what everybody needs should be in 'struct
> > dso', something one _may_ want, like data profiling, should be in
> > associated with that DSO thru some other way.
> > I'm applying this now as this is a super cool feature, but think about
> > it.
> I think I have this series applied up to this patch, the next one is not
> applying cleanly, so I'll do the usual set of build tests so that I can
> push this for linux-next consumption.
> This should be on tmp.perf-tools-next in a few jiffies, in
> perf-tools-next a bit later.
Ok, as discussed on google chat, I got v3, all is in my local tree,
build testing while I review.
- Arnaldo
Powered by blists - more mailing lists