From: Julia Lawall <julia.lawall@lip6.fr>
To: Joe Perches <joe@perches.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
Bhumika Goyal <bhumirks@gmail.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvdimm: constify device_type structures
Date: Wed, 25 Jan 2017 17:04:07 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1701251703400.3117@hadrien> (raw)
In-Reply-To: <1485360117.12563.85.camel@perches.com>
On Wed, 25 Jan 2017, Joe Perches wrote:
> On Wed, 2017-01-25 at 07:49 +0100, Julia Lawall wrote:
> > What does the data column actually represent? I tried size on the .o file
> > generated from:
> >
> > commit a65f0161f4d69d6738d4821e649448312cd818e2
> > Author: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Tue Jan 17 15:22:28 2017 +1100
> >
> > with CONFIG_X86_64=y and I get:
> >
> > text data bss dec hex filename
> > 19726 3480 16 23222 5ab6 drivers/nvdimm/namespace_devs.o
> >
> > but when I run objdump -sh drivers/nvdimm/namespace_devs.o, I find a .data
> > segment of size 1008 and a .data.unlikely segment of size 8, which don't
> > match up with the results of size.
>
> Likely you have dynamic_debug enabled and you
> need to include these additional sections:
>
> __jump_table
> __verbose
>
> If user_mode_linux is enabled, add sections:
>
> .fini_array
> .init_array
Ah, thanks for the explanations.
julia
next prev parent reply other threads:[~2017-01-25 16:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 19:24 [PATCH] nvdimm: constify device_type structures Bhumika Goyal
2017-01-24 19:58 ` Dan Williams
2017-01-25 2:37 ` Joe Perches
2017-01-25 2:40 ` Dan Williams
2017-01-25 2:49 ` Joe Perches
2017-01-25 6:49 ` Julia Lawall
2017-01-25 16:01 ` Joe Perches
2017-01-25 16:04 ` Julia Lawall [this message]
2017-01-25 16:16 ` Bhumika Goyal
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=alpine.DEB.2.20.1701251703400.3117@hadrien \
--to=julia.lawall@lip6.fr \
--cc=bhumirks@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@ml01.01.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).