From: Markus Armbruster <armbru@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-trivial@nongnu.org, duboisj@gmail.com,
qemu-devel@nongnu.org, Josh DuBois <josh@joshdubois.com>
Subject: Re: [PATCH] trace/simple: Enable tracing on startup only if the user specifies a trace option
Date: Fri, 11 Sep 2020 07:03:28 +0200 [thread overview]
Message-ID: <87ft7ohplr.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <87r1rjkrnq.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Thu, 03 Sep 2020 13:48:09 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> duboisj@gmail.com writes:
>
>> From: Josh DuBois <josh@joshdubois.com>
>>
>> Tracing can be enabled at the command line or via the
>> monitor. Command-line trace options are recorded during
>> trace_opt_parse(), but tracing is not enabled until the various
>> front-ends later call trace_init_file(). If the user passes a trace
>> option on the command-line, remember that and enable tracing during
>> trace_init_file(). Otherwise, trace_init_file() should record the
>> trace file specified by the frontend and avoid enabling traces
>> until the user requests them via the monitor.
>>
>> This fixes 1b7157be3a8c4300fc8044d40f4b2e64a152a1b4 and also
>> db25d56c014aa1a96319c663e0a60346a223b31e, by allowing the user
>> to enable traces on the command line and also avoiding
>> unwanted trace-<pid> files when the user has not asked for them.
>>
>> Fixes: 1b7157be3a8c4300fc8044d40f4b2e64a152a1b4
>> Signed-off-by: Josh DuBois <josh@joshdubois.com>
>> ---
>> trace/control.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/trace/control.c b/trace/control.c
>> index 6558b5c906..8f94f09444 100644
>> --- a/trace/control.c
>> +++ b/trace/control.c
>> @@ -39,6 +39,7 @@ static TraceEventGroup *event_groups;
>> static size_t nevent_groups;
>> static uint32_t next_id;
>> static uint32_t next_vcpu_id;
>> +static bool init_trace_on_startup;
>>
>> QemuOptsList qemu_trace_opts = {
>> .name = "trace",
>> @@ -225,7 +226,9 @@ void trace_init_file(const char *file)
>> {
>> #ifdef CONFIG_TRACE_SIMPLE
>> st_set_trace_file(file);
>> - st_set_trace_file_enabled(true);
>> + if (init_trace_on_startup) {
>> + st_set_trace_file_enabled(true);
>> + }
>> #elif defined CONFIG_TRACE_LOG
>> /*
>> * If both the simple and the log backends are enabled, "--trace file"
>> @@ -299,6 +302,7 @@ char *trace_opt_parse(const char *optarg)
>> }
>> trace_init_events(qemu_opt_get(opts, "events"));
>> trace_file = g_strdup(qemu_opt_get(opts, "file"));
>> + init_trace_on_startup = true;
>> qemu_opts_del(opts);
>>
>> return trace_file;
>
> Stops the littering for me.
>
> Stefan, please have a closer look.
Ping?
next prev parent reply other threads:[~2020-09-11 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 17:46 [PATCH] trace/simple: Enable tracing on startup only if the user specifies a trace option duboisj
2020-09-03 11:48 ` Markus Armbruster
2020-09-11 5:03 ` Markus Armbruster [this message]
2020-09-11 10:08 ` Stefan Hajnoczi
2020-09-29 7:46 ` Markus Armbruster
2020-10-20 9:19 ` Markus Armbruster
2020-10-20 19:29 ` Josh DuBois
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=87ft7ohplr.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=duboisj@gmail.com \
--cc=josh@joshdubois.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.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).