From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ohci: Split long traces to smaller ones
Date: Thu, 25 Sep 2014 19:38:36 +1000 [thread overview]
Message-ID: <5423E29C.3030902@ozlabs.ru> (raw)
In-Reply-To: <1411632559.7154.8.camel@nilsson.home.kraxel.org>
On 09/25/2014 06:09 PM, Gerd Hoffmann wrote:
> On Do, 2014-09-25 at 10:16 +1000, Alexey Kardashevskiy wrote:
>> Recent traces rework introduced 2 tracepoints with 13 and 20
>> arguments. When dtrace backend is selected
>> (--enable-trace-backend=dtrace), compile fails as
>> sys/sdt.h defines DTRACE_PROBE up to DTRACE_PROBE12 only.
>>
>> This splits long tracepoints.
>
> Can you also change the tracing-enabled check to use '#ifndef
> CONFIG_TRACE_NOP' as suggested by Stefan please?
Nope :( As I said in that thread, I am not familiar with "dtrace" - are
traces configurable with it? With --enable-trace-backend=dtrace,
trace_event_get_state is not defined so CONFIG_TRACE_NOP is not 100% equal
replacement.
--
Alexey
next prev parent reply other threads:[~2014-09-25 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 0:16 [Qemu-devel] [PATCH] ohci: Split long traces to smaller ones Alexey Kardashevskiy
2014-09-25 8:09 ` Gerd Hoffmann
2014-09-25 9:38 ` Alexey Kardashevskiy [this message]
2014-09-25 14:08 ` Gerd Hoffmann
2014-09-25 9:18 ` Alex Bennée
2014-09-25 9:38 ` [Qemu-devel] [PATCH] ohci: drop computed flags from trace events Alex Bennée
2014-09-25 10:50 ` Stefan Hajnoczi
2014-09-26 8:51 ` Stefan Hajnoczi
2014-09-26 8:51 ` [Qemu-devel] [PATCH] ohci: Split long traces to smaller ones Stefan Hajnoczi
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=5423E29C.3030902@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).