From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Mike Leach <mike.leach@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, coresight@lists.linaro.org,
suzuki.poulose@arm.com, leo.yan@linaro.org
Subject: Re: [PATCH v3 0/5] coresight: syscfg: Extend configfs for config load
Date: Fri, 27 May 2022 10:32:35 -0600 [thread overview]
Message-ID: <20220527163235.GC360589@p14s> (raw)
In-Reply-To: <20220414064457.12052-1-mike.leach@linaro.org>
On Thu, Apr 14, 2022 at 07:44:52AM +0100, Mike Leach wrote:
> This set extends the configfs support to allow loading and unloading of
> configurations as binary files via configfs.
>
> Additional attributes - load and unload are provided to in the
> configurations group to implement the load functionality.
>
> Routines to generate binary configuration files are supplied in
> ./tools/coresight.
>
> Example generator and reader applications are provided.
>
> Tools may be cross compiled or built for use on host system.
>
> Documentation is updated to describe feature usage.
I think this patchset is looking quite good now. The main issue for now is to
know if we want to keep the capability to read and print configurations. To me
it doesn't provide much for the quirks it adds, i.e patch 3.
James and/or Leo will also have to do a review. As such they should be added,
along with Arnaldo, to the next revision.
I am done reviewing this set.
Thanks,
Mathieu
>
> Changes since v2:
> 1) Rebased & tested oo coresight/next - 5.18-rc2
> 2) Moved coresight config generator and reader programs from samples to
> tools/coresight. Docs updated to match. (suggested by Mathieu)
> 3) userspace builds now use userspace headers from tools/...
> 4) Other minor fixes from Mathieu's review.
>
> Changes since v1:
> 1) Rebased to coresight/next - 5.16-rc1 with previous coresight config
> set applied.
> 2) Makefile.host fixed to default to all target.
>
> Mike Leach (5):
> coresight: configfs: Add in functionality for load via configfs
> coresight: configfs: Add in binary attributes to load files
> coresight: configfs: Modify config files to allow userspace use
> coresight: tools: Add config file write and reader tools
> Documentation: coresight: docs for config load via configfs
>
> .../trace/coresight/coresight-config.rst | 166 +++++-
> MAINTAINERS | 2 +
> drivers/hwtracing/coresight/Makefile | 2 +-
> .../coresight/coresight-config-file.c | 475 ++++++++++++++++++
> .../coresight/coresight-config-file.h | 126 +++++
> .../hwtracing/coresight/coresight-config.h | 27 +
> .../coresight/coresight-syscfg-configfs.c | 91 ++++
> .../hwtracing/coresight/coresight-syscfg.c | 37 ++
> .../hwtracing/coresight/coresight-syscfg.h | 2 +
> tools/coresight/Makefile | 51 ++
> tools/coresight/coresight-cfg-bufw.c | 303 +++++++++++
> tools/coresight/coresight-cfg-bufw.h | 26 +
> tools/coresight/coresight-cfg-example1.c | 65 +++
> tools/coresight/coresight-cfg-examples.h | 27 +
> tools/coresight/coresight-cfg-file-read.c | 197 ++++++++
> tools/coresight/coresight-cfg-filegen.c | 58 +++
> tools/include/uapi/coresight-config-uapi.h | 76 +++
> 17 files changed, 1724 insertions(+), 7 deletions(-)
> create mode 100644 drivers/hwtracing/coresight/coresight-config-file.c
> create mode 100644 drivers/hwtracing/coresight/coresight-config-file.h
> create mode 100644 tools/coresight/Makefile
> create mode 100644 tools/coresight/coresight-cfg-bufw.c
> create mode 100644 tools/coresight/coresight-cfg-bufw.h
> create mode 100644 tools/coresight/coresight-cfg-example1.c
> create mode 100644 tools/coresight/coresight-cfg-examples.h
> create mode 100644 tools/coresight/coresight-cfg-file-read.c
> create mode 100644 tools/coresight/coresight-cfg-filegen.c
> create mode 100644 tools/include/uapi/coresight-config-uapi.h
>
> --
> 2.17.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-05-27 16:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 6:44 [PATCH v3 0/5] coresight: syscfg: Extend configfs for config load Mike Leach
2022-04-14 6:44 ` [PATCH v3 1/5] coresight: configfs: Add in functionality for load via configfs Mike Leach
2022-05-11 17:58 ` Mathieu Poirier
2022-05-16 12:43 ` Mike Leach
2022-05-12 17:54 ` Mathieu Poirier
2022-05-25 17:38 ` Mathieu Poirier
2022-06-01 8:32 ` Mike Leach
2022-04-14 6:44 ` [PATCH v3 2/5] coresight: configfs: Add in binary attributes to load files Mike Leach
2022-05-25 18:00 ` Mathieu Poirier
2022-05-25 19:30 ` Mathieu Poirier
2022-06-01 8:33 ` Mike Leach
2022-04-14 6:44 ` [PATCH v3 3/5] coresight: configfs: Modify config files to allow userspace use Mike Leach
2022-05-25 19:57 ` Mathieu Poirier
2022-04-14 6:44 ` [PATCH v3 4/5] coresight: tools: Add config file write and reader tools Mike Leach
2022-05-26 17:46 ` Mathieu Poirier
2022-05-27 16:25 ` Mathieu Poirier
2022-06-01 10:56 ` Mike Leach
2022-06-01 16:10 ` Mathieu Poirier
2022-04-14 6:44 ` [PATCH v3 5/5] Documentation: coresight: docs for config load via configfs Mike Leach
2022-05-26 17:48 ` Mathieu Poirier
2022-05-10 15:39 ` [PATCH v3 0/5] coresight: syscfg: Extend configfs for config load Mathieu Poirier
2022-05-27 16:32 ` Mathieu Poirier [this message]
2022-06-01 8:30 ` Mike Leach
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=20220527163235.GC360589@p14s \
--to=mathieu.poirier@linaro.org \
--cc=coresight@lists.linaro.org \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@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;
as well as URLs for NNTP newsgroup(s).