From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH] trace-cmd: Fix kbuffer_start_of_data() to return the first record
Date: Mon, 6 Jul 2020 11:53:04 -0400 [thread overview]
Message-ID: <20200706115304.45209c2b@oasis.local.home> (raw)
In-Reply-To: <20200706154714.27566-1-tz.stoyanov@gmail.com>
On Mon, 6 Jul 2020 18:47:14 +0300
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> The first record in a ring buffer page may not allways be at the
> beginning of the page. There could be time-extends injected before it.
> In this case kbuffer_start_of_data() will not return the first record,
> as expected. Additional filed "start" is added in kbuffer struct, to hold
> the offset of the first record from the page and kbuffer_start_of_data()
> is modified to use it.
Thanks Tzvetomir,
I'm going to add a comment that this was originally taken from code I
wrote, and you cleaned it up and made it presentable. That way it
states why there's the two signed-off-bys.
-- Steve
>
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> Signed-off-by: Tzvetomir Stoyanov (VMware) <tz.stoyanov@gmail.com>
> ---
> lib/traceevent/kbuffer-parse.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/lib/traceevent/kbuffer-parse.c b/lib/traceevent/kbuffer-parse.c
> index 2c5f00a9..844db976 100644
> --- a/lib/traceevent/kbuffer-parse.c
> +++ b/lib/traceevent/kbuffer-parse.c
> @@ -35,6 +35,7 @@ enum {
> * @next - offset from @data to the start of next event
> * @size - The size of data on @data
> * @start - The offset from @subbuffer where @data lives
> + * @first - The offset from @subbuffer where the first non time stamp event lives
> *
> * @read_4 - Function to read 4 raw bytes (may swap)
> * @read_8 - Function to read 8 raw bytes (may swap)
> @@ -51,6 +52,7 @@ struct kbuffer {
> unsigned int next;
> unsigned int size;
> unsigned int start;
> + unsigned int first;
>
> unsigned int (*read_4)(void *ptr);
> unsigned long long (*read_8)(void *ptr);
> @@ -546,6 +548,9 @@ int kbuffer_load_subbuffer(struct kbuffer *kbuf, void *subbuffer)
>
> next_event(kbuf);
>
> + /* save the first record from the page */
> + kbuf->first = kbuf->curr;
> +
> return 0;
> }
>
> @@ -755,7 +760,7 @@ void kbuffer_set_old_format(struct kbuffer *kbuf)
> */
> int kbuffer_start_of_data(struct kbuffer *kbuf)
> {
> - return kbuf->start;
> + return kbuf->first + kbuf->start;
> }
>
> /**
prev parent reply other threads:[~2020-07-06 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 15:47 [PATCH] trace-cmd: Fix kbuffer_start_of_data() to return the first record Tzvetomir Stoyanov (VMware)
2020-07-06 15:53 ` 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=20200706115304.45209c2b@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.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).