mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, acme@kernel.org,
	peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com,
	masami.hiramatsu.pt@hitachi.com, wangnan0@huawei.com,
	namhyung@kernel.org, srikar@linux.vnet.ibm.com,
	naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [RFC] perf probe: Fix offline module name missmatch issue
Date: Tue, 26 Apr 2016 11:19:16 +0900	[thread overview]
Message-ID: <20160426111916.50d03e047aaed8112b235686@kernel.org> (raw)
In-Reply-To: <20160426062438.aea663884cf5bd95f766f2d5@kernel.org>

On Tue, 26 Apr 2016 06:24:38 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> > +/*
> > + * NOTE:
> > + * '.gnu.linkonce.this_module' section of kernel module elf directly
> > + * maps to 'struct module' from linux/module.h. This section contains
> > + * actual module name which will be used by kernel after loading it.
> > + * But, we cannot use 'struct module' here since linux/module.h is not
> > + * exposed to user-space. Offset of 'name' has remained same from long
> > + * time, so hardcoding it here.
> > + */

BTW, is there no way to get the module name avoiding to access
this "hidden" data structure?
This looks very tricky way...

Thanks,

-- 
Masami Hiramatsu <mhiramat@kernel.org>

  reply	other threads:[~2016-04-26  2:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 10:38 Ravi Bangoria
2016-04-25 10:38 ` [RFC] perf probe: Fix module probe issue if no dwarf support Ravi Bangoria
2016-04-25 21:29   ` Masami Hiramatsu
2016-04-26  9:04     ` Ravi Bangoria
2016-04-25 21:24 ` [RFC] perf probe: Fix offline module name missmatch issue Masami Hiramatsu
2016-04-26  2:19   ` Masami Hiramatsu [this message]
2016-04-26  9:00     ` Ravi Bangoria
2016-04-26  8:56   ` Ravi Bangoria
2016-04-26  9:15     ` Wangnan (F)
2016-04-26 10:45       ` Ravi Bangoria
2016-04-26 10:46     ` Masami Hiramatsu
2016-04-26 14:29       ` Ravi Bangoria

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=20160426111916.50d03e047aaed8112b235686@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=naveen.n.rao@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    --cc=srikar@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.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
Powered by JetHome