From: Jiri Olsa <jolsa@redhat.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: acme@kernel.org, peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
adrian.hunter@intel.com, mike.leach@arm.com,
suzuki.poulosi@arm.com, kim.phillips@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 01/10] perf tools: Integrating the CoreSight decoding library
Date: Tue, 16 Jan 2018 13:14:48 +0100 [thread overview]
Message-ID: <20180116121447.GA26643@krava> (raw)
In-Reply-To: <1516039994-314-2-git-send-email-mathieu.poirier@linaro.org>
On Mon, Jan 15, 2018 at 11:13:05AM -0700, Mathieu Poirier wrote:
> The Open CoreSight Decoding Library (openCSD) is a free and open
> library to decode traces collected by the CoreSight hardware
> infrastructure.
>
> This patch adds the required mechanic to recognise the presence
> of the openCSD library on a system and set up miscellaneous flags
> to be used in the compilation of the trace decoding feature.
>
> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> tools/build/Makefile.feature | 6 ++++--
> tools/build/feature/Makefile | 7 ++++++-
> tools/build/feature/test-all.c | 5 +++++
> tools/build/feature/test-libopencsd.c | 8 ++++++++
> tools/perf/Makefile.config | 25 +++++++++++++++++++++++++
> tools/perf/Makefile.perf | 2 ++
> 6 files changed, 50 insertions(+), 3 deletions(-)
> create mode 100644 tools/build/feature/test-libopencsd.c
>
> diff --git a/tools/build/Makefile.feature b/tools/build/Makefile.feature
> index e52fcefee379..dc3d97b248ab 100644
> --- a/tools/build/Makefile.feature
> +++ b/tools/build/Makefile.feature
> @@ -66,7 +66,8 @@ FEATURE_TESTS_BASIC := \
> bpf \
> sched_getcpu \
> sdt \
> - setns
> + setns \
> + libopencsd
please keep the space/tabs context, here and other places in this patch
thanks,
jirka
next prev parent reply other threads:[~2018-01-16 12:14 UTC|newest]
Thread overview: 27+ 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
2018-01-16 12:14 ` Jiri Olsa [this message]
2018-01-16 12:15 ` Jiri Olsa
2018-01-16 18:04 ` Mathieu Poirier
2018-01-16 20:30 ` Mathieu Poirier
2018-01-17 8:06 ` Jiri Olsa
2018-01-18 13:41 ` Arnaldo Carvalho de Melo
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
2018-01-16 12:17 ` [PATCH v2 00/10] perf tools: Add support " Jiri Olsa
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=20180116121447.GA26643@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=kim.phillips@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suzuki.poulosi@arm.com \
/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