From: Steven Rostedt <rostedt@goodmis.org>
To: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 5/7] trace-cmd library: Select the file version when writing trace file
Date: Thu, 29 Apr 2021 09:42:57 -0400 [thread overview]
Message-ID: <20210429094257.4cf3e7f2@gandalf.local.home> (raw)
In-Reply-To: <20210429040119.843617-6-tz.stoyanov@gmail.com>
On Thu, 29 Apr 2021 07:01:17 +0300
"Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com> wrote:
> index 9231c319..f36718f1 100644
> --- a/lib/trace-cmd/trace-output.c
> +++ b/lib/trace-cmd/trace-output.c
> @@ -57,6 +57,7 @@ struct tracecmd_output {
> int nr_options;
> bool quiet;
> unsigned long file_state;
> + unsigned long file_version;
> struct list_head options;
> struct tracecmd_msg_handle *msg_handle;
> char *trace_clock;
> @@ -907,6 +908,17 @@ out_free:
> return ret;
> }
>
> +static int select_file_version(struct tracecmd_output *handle,
> + struct tracecmd_input *ihandle)
> +{
> + if (ihandle)
> + handle->file_version = tracecmd_get_file_version(ihandle);
> + else
> + handle->file_version = FILE_VERSION;
> +
> + return 0;
> +}
> +
This is where we should have the logic for what we write.
We save a string where the version is going to be located. We default it to
the lowest level (6), and then if a feature is recorded that is of a higher
version, we up it, and change the number of disk as well.
If there's a case where we get to two digit strings, we should have it be:
"6 \0"
which should still work. Then if we use a feature that requires version 10,
it would be updated to:
"10\0"
We can do this at the end of recording.
-- Steve
next prev parent reply other threads:[~2021-04-29 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 4:01 [PATCH v2 0/7] Bump trace file version Tzvetomir Stoyanov (VMware)
2021-04-29 4:01 ` [PATCH v2 1/7] trace-cmd library: Remove unused private APIs for creating trace files Tzvetomir Stoyanov (VMware)
2021-04-29 4:01 ` [PATCH v2 2/7] trace-cmd: Check if file version is supported Tzvetomir Stoyanov (VMware)
2021-04-29 4:01 ` [PATCH v2 3/7] trace-cmd library: Bump the trace file version to 7 Tzvetomir Stoyanov (VMware)
2021-04-29 4:01 ` [PATCH v2 4/7] trace-cmd library: Add new API to get file version of input handler Tzvetomir Stoyanov (VMware)
2021-04-29 4:01 ` [PATCH v2 5/7] trace-cmd library: Select the file version when writing trace file Tzvetomir Stoyanov (VMware)
2021-04-29 13:42 ` Steven Rostedt [this message]
2021-04-29 4:01 ` [PATCH v2 6/7] trace-cmd library: Extend the create file APIs to support different file version Tzvetomir Stoyanov (VMware)
2021-04-29 13:50 ` Steven Rostedt
2021-04-29 4:01 ` [PATCH v2 7/7] trace-cmd record: Add new parameter --file-version Tzvetomir Stoyanov (VMware)
2021-04-29 13:54 ` Steven Rostedt
2021-05-10 6:22 ` [PATCH v2 0/7] Bump trace file version 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=20210429094257.4cf3e7f2@gandalf.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).