All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: David Ahern <dsahern@gmail.com>
Cc: cfreehill@alumni.utexas.net, Chris Freehill <cfreehill@gmail.com>,
	linux-perf-users@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: help with porting perf lkm to later kernel
Date: Thu, 29 Aug 2013 08:59:06 +0200	[thread overview]
Message-ID: <20130829065906.GU10002@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <521E81FB.2030302@gmail.com>

On Wed, Aug 28, 2013 at 05:04:27PM -0600, David Ahern wrote:
> On 8/28/13 4:53 PM, Chris Freehill wrote:
> >>I am trying to get my linux kernel module that extends perf support to work
> >>in a later kernel version. The lkm had been working in 3.0.51.
> >>
> >>In the new target kernel to which I am trying to port, 3.8.13, I get
> >>warnings at the modpost stage complaining about symbols that can no longer
> >>be found. If I attempt to load that module, I get errors saying the same
> >>thing (those symbols can't be found).
> >>
> >>The symbols that can't be found are
> >>
> >>".perf_pmu_enable"
> >>
> >>".perf_event_update_userpage"
> >>
> >>".perf_pmu_disable"
> >>
> >>".perf_event_overflow"
> >>
> >>".perf_pmu_unregister"
> >>
> >>".perf_pmu_register"
> >>
> >>Does anyone have any tips or advice as to how code that calls these
> >>previously working functions should now be handled when built against later
> >>kernels?

# git show v3.0:kernel/events/core.c | grep EXPORT_SYMBOL
EXPORT_SYMBOL_GPL(perf_event_release_kernel);
EXPORT_SYMBOL_GPL(perf_event_read_value);
EXPORT_SYMBOL_GPL(perf_register_guest_info_callbacks);
EXPORT_SYMBOL_GPL(perf_unregister_guest_info_callbacks);
EXPORT_SYMBOL_GPL(perf_swevent_get_recursion_context);
EXPORT_SYMBOL_GPL(perf_tp_event);
EXPORT_SYMBOL_GPL(perf_event_create_kernel_counter);

IOW. how can your module have ever used those functions in 3.0 ?

Typically the answer to 'why did the export get removed' is simply
'because there are no users'.

  reply	other threads:[~2013-08-29  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28 22:53 help with porting perf lkm to later kernel Chris Freehill
2013-08-28 23:04 ` David Ahern
2013-08-29  6:59   ` Peter Zijlstra [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-29 18:44 Chris Freehill
2013-08-28  2:14 Chris Freehill

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=20130829065906.GU10002@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=cfreehill@alumni.utexas.net \
    --cc=cfreehill@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.