From: Jiri Olsa <olsajiri@gmail.com>
To: Blake Jones <blakejones@google.com>
Cc: Jiri Olsa <olsajiri@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] Add a "-m" option to "perf buildid-list".
Date: Tue, 14 Jun 2022 14:29:06 +0200 [thread overview]
Message-ID: <Yqh/EkVy99Bej46S@krava> (raw)
In-Reply-To: <CAP_z_CgkJ8RgWevJnDiq-+JjB=ni0OzJ3npwW+S9RZ66i0Y3Kg@mail.gmail.com>
On Mon, Jun 13, 2022 at 03:02:39PM -0700, Blake Jones wrote:
> Thanks for taking a look at this!
>
> On Sun, Jun 12, 2022 at 3:18 PM Jiri Olsa <olsajiri@gmail.com> wrote:
> > why 'modules' ? it shows all maps (including kernel)
> > so perhaps -m/--maps would be better?
>
> I called it "modules" because it only operates on the kernel. Calling it
> "maps" would suggest to me that it might also be able to show
> information about the maps in perf.data files, which it can't (just as the
> "-k" option only operates on the kernel). Given that, does it still seem
> like "maps" would be more appropriate?
still there's kernel map included, so it's strange to me call it modules
--m/--kernel-maps ?
>
> > also please state that it's from running kernel
>
> Happy to make this change.
>
> > any reason why not use the dso fields directly?
>
> I was just following my general software engineering instincts to
> encapsulate implementation details, so that e.g. the caller doesn't need to
> know about details such as the "has_build_id" boolean. I haven't made
> changes to perf before, so if that's not the preferred style, I can do it
> a different way.
we have some helpers for dso fields, but AFAICS long_name and has_build_id
are used directly all over the place
jirka
next prev parent reply other threads:[~2022-06-14 12:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 19:15 [PATCH RESEND] Add a "-m" option to "perf buildid-list" Blake Jones
2022-06-12 22:18 ` Jiri Olsa
2022-06-13 22:02 ` Blake Jones
2022-06-14 12:29 ` Jiri Olsa [this message]
2022-06-15 0:10 ` Blake Jones
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=Yqh/EkVy99Bej46S@krava \
--to=olsajiri@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=blakejones@google.com \
--cc=irogers@google.com \
--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 \
--cc=peterz@infradead.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).