From: David Ahern <dsahern@gmail.com>
To: cfreehill@alumni.utexas.net
Cc: Chris Freehill <cfreehill@gmail.com>,
linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: help with porting perf lkm to later kernel
Date: Wed, 28 Aug 2013 17:04:27 -0600 [thread overview]
Message-ID: <521E81FB.2030302@gmail.com> (raw)
In-Reply-To: <CANFySve_0Mw48knK-1ueWjibBQfzfgLQzOhJde5zWL9OZO3iYw@mail.gmail.com>
[Added Ingo, Peter and Arnaldo for opinions on the symbol exports - or
lack of]
On 8/28/13 4:53 PM, Chris Freehill wrote:
> Another way to ask this, is why are these symbols no longer exported
> (previously exported in core.c with EXPORT_SYMBOL_GPL), and how are
> people who built lkm's using the previously existing interface
> supposed to port them? Is it perhaps documented somewhere? I have not
> been able to find this via google or in git comments.
>
> Is this the wrong forum for this question (which I grant may be a
> "newbie" question), or is there just no good answer?
>
> thanks,
> chris
>
>
>> 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?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-08-28 23:04 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 [this message]
2013-08-29 6:59 ` Peter Zijlstra
-- 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=521E81FB.2030302@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=cfreehill@alumni.utexas.net \
--cc=cfreehill@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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.