From: Steven Rostedt via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
lttng-dev <lttng-dev@lists.lttng.org>,
KVM list <kvm@vger.kernel.org>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [lttng-dev] Unexport of kvm_x86_ops vs tracer modules
Date: Mon, 25 Apr 2022 10:04:34 -0400 [thread overview]
Message-ID: <20220425100434.2f5d18bb@gandalf.local.home> (raw)
In-Reply-To: <1622857974.11247.1649441213797.JavaMail.zimbra@efficios.com>
On Fri, 8 Apr 2022 14:06:53 -0400 (EDT)
Mathieu Desnoyers <mathieu.desnoyers@efficios.com> wrote:
>
> Indeed, the fact that the TP_fast_assign snippets are embedded in the
> trace_event_raw_event_* symbols is an issue for LTTng. This ties those
> to ftrace.
Not just ftrace, perf does it too.
Now another solution is to make the fast assigns available to anyone, and
to allow you to simply pass in a pointer and size to have the data written
into it. That is, you get the results of the TRACE_EVENT and not have to
depend on internal data from the tracepoint.
-- Steve
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2022-04-25 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 15:36 [lttng-dev] Unexport of kvm_x86_ops vs tracer modules Mathieu Desnoyers via lttng-dev
2022-04-08 16:24 ` Paolo Bonzini via lttng-dev
2022-04-08 18:06 ` Mathieu Desnoyers via lttng-dev
2022-04-25 13:00 ` Mathieu Desnoyers via lttng-dev
2022-04-25 13:28 ` Paolo Bonzini via lttng-dev
2022-04-25 14:04 ` Steven Rostedt via lttng-dev [this message]
2022-04-25 16:02 ` Mathieu Desnoyers via lttng-dev
2022-04-25 19:13 ` Steven Rostedt via lttng-dev
2022-04-26 6:36 ` Paolo Bonzini via lttng-dev
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=20220425100434.2f5d18bb@gandalf.local.home \
--to=lttng-dev@lists.lttng.org \
--cc=kvm@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=pbonzini@redhat.com \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.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).