From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library
Date: Thu, 18 Jan 2018 10:41:39 -0300 [thread overview]
Message-ID: <20180118134139.GC18383@kernel.org> (raw)
In-Reply-To: <20180117080640.GD6183@krava>
Em Wed, Jan 17, 2018 at 09:06:40AM +0100, Jiri Olsa escreveu:
> On Tue, Jan 16, 2018 at 01:30:33PM -0700, Mathieu Poirier wrote:
> > On 16 January 2018 at 05:15, Jiri Olsa <jolsa@redhat.com> wrote:
> > > On Mon, Jan 15, 2018 at 11:13:05AM -0700, Mathieu Poirier wrote:
> > >> +++ b/tools/build/Makefile.feature
> > >> @@ -66,7 +66,8 @@ FEATURE_TESTS_BASIC := \
> > >> bpf \
> > >> sched_getcpu \
> > >> sdt \
> > >> - setns
> > >> + setns \
> > >> + libopencsd
> > >>
> > >> # FEATURE_TESTS_BASIC + FEATURE_TESTS_EXTRA is the complete list
> > >> # of all feature tests
> > >> @@ -108,7 +109,8 @@ FEATURE_DISPLAY ?= \
> > >> zlib \
> > >> lzma \
> > >> get_cpuid \
> > >> - bpf
> > >> + bpf \
> > >> + libopencsd
> > > we put in this list only generic libraries, this one seems arch
> > > specific please put it into FEATURE_TESTS_EXTRA list
> > I was thinking that libopencsd should fall in the same category as
> > libunwind-arm and libunwind-aarch64. Both are not architecture
> > specific and used to process traces acquired on ARM platforms. As
> > such I suggest to keep libopencsd as part of FEATURE_TESTS_BASIC and
> > remove it from under FEATURE_DISPLAY - how does that sound to you?
> ok, that sounds good
Hi Jiri,
Shouldn't libopencsd be treated like libbabeltrace was before
the required version was widely available in distros?
I.e. these csets should have the rationale for that:
Enabling it once it became widely available:
24787afbcd01 ("perf tools: Enable LIBBABELTRACE by default")
Disabling it because we would need to get things from tarballs/git
repos, build it in our machines, as requested by Ingo:
6ab2b762befd ("perf build: Disable libbabeltrace check by default")
- Arnaldo
next prev parent reply other threads:[~2018-01-18 13:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 18:13 [PATCH v2 00/10] perf tools: Add support for CoreSight trace decoding Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library Mathieu Poirier
[not found] ` <20180116121500.GB26643@krava>
[not found] ` <CANLsYkyEnJ5QzYyuGwhCB5p_2mE+8DdjaU6=Vpa6=CeKR+DzWg@mail.gmail.com>
2018-01-17 8:06 ` Jiri Olsa
2018-01-18 13:41 ` Arnaldo Carvalho de Melo [this message]
2018-01-18 13:59 ` Jiri Olsa
2018-01-18 14:14 ` Arnaldo Carvalho de Melo
2018-01-18 14:27 ` Jiri Olsa
2018-01-19 14:58 ` Arnaldo Carvalho de Melo
2018-01-19 15:12 ` Jiri Olsa
2018-01-19 15:24 ` Mathieu Poirier
2018-01-19 15:55 ` Arnaldo Carvalho de Melo
2018-01-19 17:28 ` Mathieu Poirier
2018-01-19 18:46 ` Jiri Olsa
2018-01-15 18:13 ` [PATCH v2 02/10] perf tools: Add initial entry point for decoder CoreSight traces Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 03/10] perf tools: Add processing of coresight metadata Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 04/10] perf tools: Add decoder mechanic to support dumping trace data Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 05/10] perf tools: Add support for decoding CoreSight " Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 06/10] perf tools: Add functionality to communicate with the openCSD decoder Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 07/10] pert tools: Add queue management functionality Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 08/10] perf tools: Add full support for CoreSight trace decoding Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 09/10] perf tools: Add mechanic to synthesise CoreSight trace packets Mathieu Poirier
2018-01-15 18:13 ` [PATCH v2 10/10] MAINTAINERS: Adding entry for CoreSight trace decoding Mathieu Poirier
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=20180118134139.GC18383@kernel.org \
--to=acme@kernel.org \
--cc=linux-arm-kernel@lists.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).