From: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] kernel-shark-qt: Add I/O for configuration data.
Date: Fri, 17 Aug 2018 17:13:23 +0300 [thread overview]
Message-ID: <38b58799-95e7-53c0-8398-2b590dfb1192@gmail.com> (raw)
In-Reply-To: <20180817084958.11361418@gandalf.local.home>
On 17.08.2018 15:49, Steven Rostedt wrote:
>> Hi Steven
>>
>> On 16.08.2018 21:52, Steven Rostedt wrote:
>>>> + jfile_name = json_object_new_string(file);
>>>> + jtime = json_object_new_int64(st.st_mtime);
>>> BTW, are you saving the timestamp to make sure the trace.dat file is
>>> the same? (assuming that the 'file' in question is trace.dat)
>>>
>>> What if we want to use the same "session" for different trace.dat files?
>>>
>>
>> If the timestamp is different then the import will fail (see below).
>>
>> If you really want to load the session with a different file you can
>> hand-edit the Json file and make it match.
This applies only if you want to save the entire session. The
configuration of the session contains number of file-specific values,
like PIDs, trace timestamps, marker settings (array indexes) etc.
Because of this it doesn't make sense to open a session with a different
file.
> I don't think that's very user friendly.
>
> When debugging a problem, I will create several trace files, and use
> basically the same filter for all of them. I would like to easily be
> able to create a complex filter, save it, then reuse it for the next
> trace.dat file I open. Hand modifying a timestamp will not be an option.
>
The flexibility of the configuration I/O comes in handy here. The GUI
has a Filter Import / Export menus. In this case only the settings of
the Event filter and the Adv. filter are saved to the Json file.
Thanks!
Yordan
next prev parent reply other threads:[~2018-08-17 17:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:07 [PATCH v3 1/3] kernel-shark-qt: Add Json-C as a third party dependency Yordan Karadzhov (VMware)
2018-08-16 15:07 ` [PATCH v3 2/3] kernel-shark-qt: Add I/O for configuration data Yordan Karadzhov (VMware)
2018-08-16 18:52 ` Steven Rostedt
2018-08-17 9:32 ` Yordan Karadzhov (VMware)
2018-08-17 12:49 ` Steven Rostedt
2018-08-17 14:13 ` Yordan Karadzhov (VMware) [this message]
2018-08-17 14:58 ` Steven Rostedt
2018-08-17 15:09 ` Yordan Karadzhov (VMware)
2018-08-17 15:12 ` Steven Rostedt
2018-08-17 15:29 ` Yordan Karadzhov (VMware)
2018-08-17 15:34 ` Steven Rostedt
2018-08-17 9:34 ` Yordan Karadzhov (VMware)
2018-08-17 12:52 ` Steven Rostedt
2018-08-17 14:15 ` Yordan Karadzhov (VMware)
2018-08-16 15:07 ` [PATCH v3 3/3] kernel-shark-qt: Add an example showing how to import/export config. data Yordan Karadzhov (VMware)
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=38b58799-95e7-53c0-8398-2b590dfb1192@gmail.com \
--to=y.karadz@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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).