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: Matt Helsley <mhelsley@vmware.com>,
	"linux-trace-devel@vger.kernel.org" 
	<linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH v4] tools/lib/traceevent: Change description of few APIs
Date: Tue, 19 Mar 2019 12:43:38 -0400	[thread overview]
Message-ID: <20190319124338.44e49ac4@gandalf.local.home> (raw)
In-Reply-To: <CACqStofty+o7r_RasESWrv5PA8-hvXWFG+ha76Pf-6A+GZuaYw@mail.gmail.com>

On Tue, 19 Mar 2019 10:35:05 +0000
Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:

> On Mon, Mar 18, 2019 at 11:03 PM Matt Helsley <mhelsley@vmware.com> wrote:
> >
> >
> >  
> > > On Mar 15, 2019, at 1:11 AM, Tzvetomir Stoyanov <tstoyanov@vmware.com> wrote:
> > >
> > > APIs descriptions should describe the purpose of the
> > > function, its parameters and return value. While working
> > > on man pages implementation, I noticed mismatches in the
> > > descriptions of few APIs. This patch changes the description
> > > of these APIs, making them consistent with the man pages:
> > > tep_print_num_field(), tep_print_func_field(),
> > > tep_get_header_page_size(), tep_get_long_size(),
> > > tep_set_long_size(), tep_get_page_size() and
> > > tep_set_page_size().
> > >
> > > Signed-off-by: Tzvetomir Stoyanov <tstoyanov@vmware.com>
> > > ---
> > > tools/lib/traceevent/event-parse-api.c | 21 ++++++++++++---------
> > > tools/lib/traceevent/event-parse.c     |  4 ++--
> > > 2 files changed, 14 insertions(+), 11 deletions(-)
> > >
> > > diff --git a/tools/lib/traceevent/event-parse-api.c b/tools/lib/traceevent/event-parse-api.c
> > > index d4368dcc16ea..2d5d3642e3e9 100644
> > > --- a/tools/lib/traceevent/event-parse-api.c
> > > +++ b/tools/lib/traceevent/event-parse-api.c
> > > @@ -100,10 +100,10 @@ tep_data2host8(struct tep_handle *pevent, unsigned long long data)
> > > }
> > >
> > > /**
> > > - * tep_get_header_page_size - get size of the header page
> > > + * tep_get_header_page_size - get the size of a long integer, in kernel context  
> >
> > Just want to check If this comment change correct. Given the function name it looks a bit odd compared to the comment for tep_get_long_size().  
> 
> It is a copy / paste error,

Hmm, the function name is very confusing, as it is returning the kernel
context long size. Perhaps we should rename it to:

tep_get_header_long_size()

-- Steve

> Thanks Matt
> 
> 
> >  
> > >  * @pevent: a handle to the tep_handle
> > >  *
> > > - * This returns size of the header page
> > > + * This returns the size of a long integer, in kernel context
> > >  * If @pevent is NULL, 0 is returned.
> > >  */
> > > int tep_get_header_page_size(struct tep_handle *pevent)
> > > @@ -140,10 +140,11 @@ void tep_set_cpus(struct tep_handle *pevent, int cpus)
> > > }
> > >
> > > /**
> > > - * tep_get_long_size - get the size of a long integer on the current machine
> > > + * tep_get_long_size - get the size of a long integer on the traced machine
> > >  * @pevent: a handle to the tep_handle
> > >  *
> > > - * This returns the size of a long integer on the current machine
> > > + * This returns the size of a long integer on the machine,
> > > + * where the trace is generated
> > >  * If @pevent is NULL, 0 is returned.
> > >  */  
> 
> 
> 
> --
> 
> Tzvetomir (Ceco) Stoyanov
> VMware Open Source Technology Center


      reply	other threads:[~2019-03-19 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-15  8:11 [PATCH v4] tools/lib/traceevent: Change description of few APIs Tzvetomir Stoyanov
2019-03-18 21:03 ` Matt Helsley
2019-03-19 10:35   ` Tzvetomir Stoyanov
2019-03-19 16:43     ` Steven Rostedt [this message]

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=20190319124338.44e49ac4@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhelsley@vmware.com \
    --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).