Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 3/5] optee-benchmark: new package
Date: Mon, 10 Dec 2018 22:59:55 +0100	[thread overview]
Message-ID: <20181210225955.589c8f58@windsurf> (raw)
In-Reply-To: <1542990817-28362-3-git-send-email-etienne.carriere@linaro.org>

Hello Etienne,

On Fri, 23 Nov 2018 17:33:35 +0100, Etienne Carriere wrote:
> OP-TEE performance benchmark tools for the OP-TEE project.
> 
> This packages generates embedded Linux based OS materials used
> to retrieve execution timing information on invocation of the
> OP-TEE secure services.
> 
> It is added next to the OP-TEE client package in BR configuration.
> 
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>

Thanks. I have pretty much the same comments as for PATCH 2/5 on
optee-client, so if you could apply the same logic to this PATCH 3/5,
it would be nice. A few other things though.

>  package/Config.in                            |  1 +
>  package/optee-benchmark/Config.in            | 69 ++++++++++++++++++++++++++++
>  package/optee-benchmark/optee-benchmark.hash |  2 +
>  package/optee-benchmark/optee-benchmark.mk   | 22 +++++++++
>  4 files changed, 94 insertions(+)

Please add an entry in the DEVELOPERS file (it should be done in each
patch for the package being added by that patch).

> diff --git a/package/optee-benchmark/Config.in b/package/optee-benchmark/Config.in
> new file mode 100644
> index 0000000..2d56a7e
> --- /dev/null
> +++ b/package/optee-benchmark/Config.in
> @@ -0,0 +1,69 @@
> +config BR2_PACKAGE_OPTEE_BENCHMARK
> +	bool "Embed OP-TEE benchmark support"
> +	select BR2_PACKAGE_OPTEE_CLIENT
> +	select BR2_PACKAGE_LIBYAML
> +	help
> +	  Enable the OP-TEE benchmark package that brings facilities
> +	  for profiling traversal and execution timings when
> +	  invoking OP-TEE. OP-TEE benchmark is a component delivered
> +	  by the OP-TEE project.
> +
> +	  http://github.com/linaro-swg/optee_benchmark
> +
> +if BR2_PACKAGE_OPTEE_BENCHMARK
> +
> +choice
> +	prompt "OP-TEE Benchmark version"
> +	default BR2_PACKAGE_OPTEE_BENCHMARK_LATEST
> +	help
> +	  Select the version of OP-TEE benchmark you want to use
> +
> +config BR2_PACKAGE_OPTEE_BENCHMARK_LATEST
> +	bool "sync with latest release tag"
> +	help
> +	  Sync on latest release tag. This currently fetches the
> +	  latest registered release tag from the OP-TEE official
> +	  Git repository.
> +
> +config BR2_PACKAGE_OPTEE_BENCHMARK_CUSTOM_GIT
> +	bool "sync with a specific Git"
> +	help
> +	  Sync with a specific OP-TEE Git repository.

Do we really need all this version customization stuff for
optee-benchmark ? I doubt it is needed. Buildroot generally doesn't
provide a version selection, except for highly HW-specific packages
(kernel, bootloaders, firmware, etc.).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-12-10 21:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1542900177-17343>
2018-11-23 16:33 ` [Buildroot] [PATCH v2 1/5] boot/optee-os: new package Etienne Carriere
2018-11-23 16:33   ` [Buildroot] [PATCH v2 2/5] optee-client: " Etienne Carriere
2018-12-10 21:57     ` Thomas Petazzoni
2018-12-12  9:27       ` Etienne Carriere
2018-12-12 15:49       ` Etienne Carriere
2018-11-23 16:33   ` [Buildroot] [PATCH v2 3/5] optee-benchmark: " Etienne Carriere
2018-12-10 21:59     ` Thomas Petazzoni [this message]
2018-12-12  9:30       ` Etienne Carriere
2018-12-13  8:27         ` Etienne Carriere
2018-11-23 16:33   ` [Buildroot] [PATCH v2 4/5] optee-examples: " Etienne Carriere
2018-11-23 16:33   ` [Buildroot] [PATCH v2 5/5] optee-test: " Etienne Carriere
2018-12-10 21:46   ` [Buildroot] [PATCH v2 1/5] boot/optee-os: " Thomas Petazzoni
2018-12-12  9:24     ` Etienne Carriere
2018-11-22 15:22 [Buildroot] [PATCH 3/5] optee-benchmark: " Etienne Carriere
2018-11-23 18:10 ` [Buildroot] [PATCH v2 " Etienne Carriere

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=20181210225955.589c8f58@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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