linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tzvetomir Stoyanov <tstoyanov@vmware.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] tools/lib/traceevent: Implement new traceevent APIs for accessing struct tep_handler fields
Date: Fri, 22 Mar 2019 10:25:21 -0400	[thread overview]
Message-ID: <20190322102521.510691f2@gandalf.local.home> (raw)
In-Reply-To: <20190322130742.13753-4-tstoyanov@vmware.com>

On Fri, 22 Mar 2019 15:07:42 +0200
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:

> As struct tep_handler definition is not exposed as part of libtraceevent API, its fields
> cannot be accessed directly by the library users. This patch implements new APIs, which
> can be used to access the struct tep_handler fields:
> tep_clear_flag(), tep_test_flag(), tep_set_parsing_failures(), tep_get_parsing_failures()
> tep_get_header_page_ts_size(), tep_is_old_format(), tep_set_print_raw() and tep_set_test_filters()

Also, I want to get out of the habit of just listing what changed, and
having a more descriptive change log. It was fine for man pages, but
for adding or modifying the actual code, it needs more detail. Like:

This patch implements new APIs which can be used to access the struct
tep_handle fields:

 tep_get_event() - retrieves an event pointer at a specific index

  modify tep_get_first_event() to use tep_get_event()

 tep_clear_flag() - clears a a tep handle flag

[ BTW, you have in the patch "tep_clear_flags" let's not have it be
  plural. Otherwise we should not be an enum. ]

 tep_test_flag() - test if a given flag is set

 tep_get_header_page_ts_size() - ...

  [ Wait! we are renaming this one. Let's use the new name ]

 tep_get_header_timestamp_size() - returns the size of the timestamp
				   stored in the header.

 tep_get_cpus - returns the number of CPUs

 tep_set_parsing_failures() - internal use function for setting failures

 tep_get_parsing_failures() - Returns what was set above

 tep_is_old_format() - Returns true if data was created by an older
		       kernel with the old data format

 tep_set_print_raw() - Have the output print in the raw format

 tep_set_test_filters() - debugging utility for testing tep filters

-- Steve


> 
> Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>


  reply	other threads:[~2019-03-22 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-22 13:07 [PATCH v2 0/3] Few patches, related to libtracevent APIs Tzvetomir Stoyanov
2019-03-22 13:07 ` [PATCH v2 1/3] tools/lib/traceevent: Change description of few APIs Tzvetomir Stoyanov
2019-03-22 13:34   ` Steven Rostedt
2019-03-22 13:07 ` [PATCH v2 2/3] tools/lib/traceevent: Coding style fixes Tzvetomir Stoyanov
2019-03-22 13:07 ` [PATCH v2 3/3] tools/lib/traceevent: Implement new traceevent APIs for accessing struct tep_handler fields Tzvetomir Stoyanov
2019-03-22 14:25   ` Steven Rostedt [this message]
2019-03-22 15:20   ` Steven Rostedt
2019-03-22 15:38     ` Tzvetomir Stoyanov

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=20190322102521.510691f2@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=tstoyanov@vmware.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).