Hi -
> > Maybe add a comment? (no need to repost if you agree):
> >
> ># Workaround to avoid dtrace(1) produces file with 'hidden'
> ># symbol visibility, define STAP_SDT_V2 to produce 'default'
> ># symbol visibility instead.
> >
> > > +QEMU_CFLAGS="$QEMU_CFLAGS -DSTAP
Hi -
On Fri, Mar 21, 2014 at 04:28:24PM +0100, Stefan Hajnoczi wrote:
> SystemTap sdt.h sometimes results in compiled probes without sufficient
> information to extract arguments. See code comment for details on this
> workaround.
>
> This patch fixes the apic_reset_irq_delivered() trace event on
Hi -
On Tue, Nov 08, 2011 at 11:22:35AM +0100, Ingo Molnar wrote:
> [...] These examples show *PICTURE PERFECT* forwards ABI
> compatibility, using the ancient perf tool on a bleeding edge
> kernel. [...]
Almost: they demonstrate that those parts of the ABI that these
particular perf commands r
Ingo Molnar writes:
> [...]
>> It's problem enough that there's no way to know what version of the
>> perf_event abi you are running against and we have to guess based
>> on kernel version. This gets "fun" because all of the vendors have
>> backported seemingly random chunks of perf_event cod
$
From: f...@redhat.com (Frank Ch. Eigler)
Date: Sun, 06 Nov 2011 17:08:48 -0500
In-Reply-To:
(Pekka
Enberg's message of "Sun, 6 Nov 2011 20:05:45 +0200")
Message-ID:
User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/pl
Stefan Hajnoczi writes:
> [...]
> Where are you putting your SystemTap scripts? I suggest creating a
> public git repo and adding a link from the QEMU wiki tracing page:
> http://wiki.qemu.org/Features/Tracing
>
> Perhaps we could even include them in a contrib/ or similar directory
> in qemu.gi
