[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <y0m4p6h8zkz.fsf@ton.toronto.redhat.com>
Date: Tue, 22 Jul 2008 15:54:04 -0400
From: fche@...hat.com (Frank Ch. Eigler)
To: Avi Kivity <avi@...ranet.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
akpm@...ux-foundation.org, Ingo Molnar <mingo@...e.hu>,
linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>, kvm@...r.kernel.org
Subject: Re: [patch 0/4] Port KVM-trace to tracepoints
Avi Kivity <avi@...ranet.com> writes:
> [...]
>> Have you considered using trace_mark() directly - eliminating the
>> KVM_TRACEN() middlemen?
> [...]
> Using trace_mark() directly -- looking at it, seems to fit the
> requirements exactly. Should have looked at it earlier. Is there a
> way to get a list of all markers?
>From kernel-space, I can't find just now an API for listing them, but
there probably is / could be one.
>From user-space, lttng tools can probably do it. systemtap can too:
% stap -l 'kernel.mark("*")'
You could prototype binary tracing thusly:
% stap -e 'probe kernel.mark("kvm_foobar") {
printf("%4b%4b%4b", # three 4-byte ints
cpu(), $arg1, $arg2)
}'
> Perhaps the kvmtrace marker->relay integration should be made a marker
> feature, since there is nothing specific to kvm in it.
Right, I believe something like that is in the lttng patch suite.
- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists