linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jon.medhurst@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: [ltt-dev] LTTng 2.0 on ARM
Date: Sat, 17 Sep 2011 15:34:42 +0100	[thread overview]
Message-ID: <1316270082.3681.20.camel@computer2> (raw)
In-Reply-To: <20110916162507.GB2100@arm.com>

On Fri, 2011-09-16 at 17:25 +0100, Dave Martin wrote:
> On Wed, Sep 14, 2011 at 05:27:08PM +0100, Jon Medhurst (Tixy) wrote:
> > This is the same issue I found recently with kprobes [1]. There is also
> > an inconsistency as function symbols in loadable module do have bit zero
> > set, but if the module is built-in then bit zero is clear. 
> 
> Does that mean that some different infrastructure is used to get the module
> symbols compared with kallsyms?

Yes, there's different infrastructure to handle symbols in loadable
modules compared to those in the kernel binary. I mentioned this in [1],
or in your Linaro inbox on 29th Aug ;-)

>   That feels nasty -- they should at least
> be consistent...

I agree, getting them consistent would solve half the problem.

-- 
Tixy


[1] http://www.spinics.net/lists/arm-kernel/msg138283.html

      reply	other threads:[~2011-09-17 14:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E68559A.8080204@linaro.org>
     [not found] ` <BLU0-SMTP86E263003FB9999131E2A196000@phx.gbl>
     [not found]   ` <4E6E4250.2000309@linaro.org>
     [not found]     ` <BLU0-SMTP6FB53F86865C7F0175B0D96020@phx.gbl>
     [not found]       ` <4E6F3B93.5050603@linaro.org>
     [not found]         ` <BLU0-SMTP720ADD6D0D065018E5C97196050@phx.gbl>
2011-09-13 17:44           ` [ltt-dev] LTTng 2.0 on ARM Rabin Vincent
2011-09-14 10:09             ` Dave Martin
2011-09-14 16:27               ` Jon Medhurst (Tixy)
2011-09-16 16:25                 ` Dave Martin
2011-09-17 14:34                   ` Jon Medhurst (Tixy) [this message]

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=1316270082.3681.20.camel@computer2 \
    --to=jon.medhurst@linaro.org \
    --cc=linux-arm-kernel@lists.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 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).