Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini via lttng-dev <lttng-dev@lists.lttng.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: Sean Christopherson <seanjc@google.com>,
	lttng-dev <lttng-dev@lists.lttng.org>,
	rostedt <rostedt@goodmis.org>, KVM list <kvm@vger.kernel.org>
Subject: Re: [lttng-dev] Unexport of kvm_x86_ops vs tracer modules
Date: Mon, 25 Apr 2022 15:28:03 +0200	[thread overview]
Message-ID: <6f716388-ea25-288a-847e-c602051157b6@redhat.com> (raw)
In-Reply-To: <358746537.34457.1650891622938.JavaMail.zimbra@efficios.com>

On 4/25/22 15:00, Mathieu Desnoyers wrote:
> We are at 5.18-rc4 now. Should I expect this unexport to stay in place
> for 5.18 final and go ahead with using kallsyms to find this symbol from
> lttng-modules instead ?

Yes, I don't think honestly that there's any reason to have the symbols 
in place for out-of-tree modules.  I would have hoped Steven to chime 
in, but this also does not seem to be one of the cases where using 
trace_*_enabled() is the way to go.

Paolo

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2022-04-25 13:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 15:36 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 [this message]
2022-04-25 14:04     ` Steven Rostedt via lttng-dev
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=6f716388-ea25-288a-847e-c602051157b6@redhat.com \
    --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