From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lluís <xscript@gmx.net>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 5/6] trace-state: [simple] add "-trace events" argument to control initial state
Date: Wed, 6 Apr 2011 21:30:58 +0100 [thread overview]
Message-ID: <BANLkTimsbG+rRrKgnLsJJvkVkTnc+xm3Fw@mail.gmail.com> (raw)
In-Reply-To: <874o6bbh4j.fsf@ginnungagap.bsc.es>
On Wed, Apr 6, 2011 at 3:15 PM, Lluís <xscript@gmx.net> wrote:
> Stefan Hajnoczi writes:
>
>>> + if (len > 1) { /* skip empty lines */
>>> + line[len - 1] = '\0';
>>> + if (!st_change_trace_event_state(line, true)) {
>
>> The build breaks when --enable-trace-backend != simple because this
>> code is outside an #ifdef CONFIG_SIMPLE_TRACE. Please add this:
>
>> diff --git a/simpletrace.h b/simpletrace.h
>> index 8d893bd..5d9d2ec 100644
>> --- a/simpletrace.h
>> +++ b/simpletrace.h
>> @@ -43,6 +43,11 @@ static inline bool st_init(const char *file)
>> {
>> return true;
>> }
>> +
>> +static bool st_change_trace_event_state(const char *tname, bool tstate)
>> +{
>> + return true;
>> +}
>> #endif /* !CONFIG_SIMPLE_TRACE */
>
>> #endif /* SIMPLETRACE_H */
>
> Hmmm... why don't simply conditionally call st_init (put it into an
> #ifdef) and remove the "#else" in simpletrace.h.
>
> I've looked at it and it's not called from anywhere else.
The benefit to stubbing out these functions is that callers don't have
#ifdefs. And caller code is always built (i.e. syntax checked by the
parser) so it helps avoid bitrot. vl.c:main() is already a long and
ugly function so it would be nice to avoid #ifdefs there.
> This also reminds me that I didn't see any "-trace" option parsing in
> the OS-specific frontends (at least in linux-user).
User emulation does not have any way to control simpletrace today.
Stefan
next prev parent reply other threads:[~2011-04-06 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 21:49 [Qemu-devel] [RFC][PATCH 0/6] trace-state: make the behaviour of "disable" consistent across all backends Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 1/6] trace: [ust] fix generation of 'trace.c' on events without args Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 2/6] trace: generalize the "property" concept in the trace-events file Lluís
2011-04-06 10:53 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-04 21:49 ` [Qemu-devel] [PATCH 3/6] trace-state: always use the "nop" backend on events with the "disable" keyword Lluís
2011-04-06 11:04 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-04 21:49 ` [Qemu-devel] [PATCH 4/6] trace-state: [simple] disable all trace points by default Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 5/6] trace-state: [simple] add "-trace events" argument to control initial state Lluís
2011-04-06 11:37 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-06 14:15 ` Lluís
2011-04-06 20:30 ` Stefan Hajnoczi [this message]
2011-04-06 21:45 ` Lluís
2011-04-04 21:49 ` [Qemu-devel] [PATCH 6/6] trace: enable all events Lluís
2011-04-06 11:38 ` [Qemu-devel] " Stefan Hajnoczi
2011-04-05 13:30 ` [Qemu-devel] Re: [RFC][PATCH 0/6] trace-state: make the behaviour of "disable" consistent across all backends Stefan Hajnoczi
2011-04-06 11:42 ` Stefan Hajnoczi
2011-04-06 14:30 ` Fabien Chouteau
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=BANLkTimsbG+rRrKgnLsJJvkVkTnc+xm3Fw@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=xscript@gmx.net \
/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).