Re: [PATCH 13/52] perf annotate-data: Add dso->data_types tree
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 13/52] perf annotate-data: Add dso->data_types tree
- From: Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>
- Date: Thu, 21 Dec 2023 17:32:44 -0300
- Cc: Jiri Olsa <jolsa@xxxxxxxxxx>, Peter Zijlstra <peterz@xxxxxxxxxxxxx>, Ian Rogers <irogers@xxxxxxxxxx>, Adrian Hunter <adrian.hunter@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-perf-users@xxxxxxxxxxxxxxx, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, Stephane Eranian <eranian@xxxxxxxxxx>, Masami Hiramatsu <mhiramat@xxxxxxxxxx>, Andi Kleen <ak@xxxxxxxxxxxxxxx>, linux-trace-devel@xxxxxxxxxxxxxxx, linux-toolchains@xxxxxxxxxxxxxxx
- In-reply-to: <ZYScVwzbviHyVFHb@kernel.org>
- References: <20231110000012.3538610-1-namhyung@kernel.org> <20231110000012.3538610-14-namhyung@kernel.org> <ZYSbzZv-Y-j0_feZ@kernel.org> <ZYScVwzbviHyVFHb@kernel.org>
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
[Index of Archives]
[Linux USB Development]
[Linux USB Development]
[Linux Audio Users]
[Yosemite Hiking]
[Linux Kernel]
[Linux SCSI]