From: Stevie Alvarez <stevie.6strings@gmail.com>
To: linux-trace-devel@vger.kernel.org
Cc: "Stevie Alvarez (Google)" <stevie.6strings@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ross Zwisler <zwisler@google.com>
Subject: [PATCH v2 0/5] histograms: bug fixes and convention compliance
Date: Thu, 3 Aug 2023 18:53:58 -0400 [thread overview]
Message-ID: <20230803225413.40697-1-stevie.6strings@gmail.com> (raw)
From: "Stevie Alvarez (Google)" <stevie.6strings@gmail.com>
Changes in v2:
* Renamed interface from histograms.h to traceeval-hist.h.
* Internal traceeval_type arrays terminated by size rather than type.
* type_alloc() guarantees traceeval_type name field is a valid pointer.
* traceeval_release() sets released pointers to NULL.
* Conditional simplifications and fixes across the board.
* Removed function stubs and their interface definitions.
* Added a timestamp flag.
* Added typedefs for traceeval_dynamic helper function signatures.
* Documentation follows established conventions (kernel docs, line comments).
* Documentation moved from interface to source code.
* Internal testing interface.
* General documentation spell checking.
Since the addition of the traceeval_dynamic function signature typedefs,
warnings pertaining to these function signatures and traceeval_type have
popped up. Steven, Ross, and anyone else, any ideas on why these
warnings are showing up?
Warning from function signatures in include/traceeval-hist.h, line 65 and 69:
warning: ‘struct traceeval_type’ declared inside parameter list will
not be visible outside of this definition or declaration
struct traceeval_type *);
Warning from dyn_release call in src/histograms.c line 258:
warning: passing argument 2 of
‘(defs + (sizetype)(i * 48))->dyn_release’ from incompatible
pointer type
defs[i].dyn_release(data[i].dyn_data, &defs[i]);
note: expected ‘struct traceeval_type *’ but argument is of type
‘struct traceeval_type *’
Warning from dyn_cmp call in src/histograms.c line 409:
warning: passing argument 3 of ‘type->dyn_cmp’ from incompatible
pointer type
return type->dyn_cmp(orig->dyn_data, copy->dyn_data, type);
note: expected ‘struct traceeval_type *’ but argument is of type
‘struct traceeval_type *’
---
v1 discussion: https://lore.kernel.org/linux-trace-devel/20230731212542.3fb668b1@gandalf.local.home/T/
Stevie Alvarez (Google) (5):
histograms: Initial histograms interface
histograms: Add traceeval initialize
histograms: Add traceeval release
histograms: Add traceeval compare
histograms: Initial unit tests
Makefile | 2 +-
include/traceeval-hist.h | 135 ++++++++++
include/traceeval-test.h | 15 ++
src/Makefile | 1 +
src/histograms.c | 522 +++++++++++++++++++++++++++++++++++++++
utest/.gitignore | 1 +
utest/Makefile | 35 +++
utest/eval-test.h | 13 +
utest/eval-utest.c | 28 +++
utest/traceeval-utest.c | 217 ++++++++++++++++
10 files changed, 968 insertions(+), 1 deletion(-)
create mode 100644 include/traceeval-hist.h
create mode 100644 include/traceeval-test.h
create mode 100644 src/histograms.c
create mode 100644 utest/.gitignore
create mode 100644 utest/Makefile
create mode 100644 utest/eval-test.h
create mode 100644 utest/eval-utest.c
create mode 100644 utest/traceeval-utest.c
--
2.41.0
next reply other threads:[~2023-08-03 22:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 22:53 Stevie Alvarez [this message]
2023-08-03 22:53 ` [PATCH v2 1/5] histograms: Initial histograms interface Stevie Alvarez
2023-08-04 13:50 ` Steven Rostedt
2023-08-04 17:41 ` Stevie Alvarez
2023-08-04 17:57 ` Steven Rostedt
2023-08-04 18:25 ` Stevie Alvarez
2023-08-03 22:54 ` [PATCH v2 2/5] histograms: Add traceeval initialize Stevie Alvarez
2023-08-04 14:40 ` Steven Rostedt
2023-08-04 18:23 ` Stevie Alvarez
2023-08-04 19:20 ` Steven Rostedt
2023-08-03 22:54 ` [PATCH v2 3/5] histograms: Add traceeval release Stevie Alvarez
2023-08-04 14:55 ` Steven Rostedt
2023-08-03 22:54 ` [PATCH v2 4/5] histograms: Add traceeval compare Stevie Alvarez
2023-08-04 15:24 ` Steven Rostedt
2023-08-07 23:40 ` Ross Zwisler
2023-08-03 22:54 ` [PATCH v2 5/5] histograms: Initial unit tests Stevie Alvarez
2023-08-04 12:37 ` [PATCH v2 0/5] histograms: bug fixes and convention compliance Steven Rostedt
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=20230803225413.40697-1-stevie.6strings@gmail.com \
--to=stevie.6strings@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=zwisler@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.