From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751450AbdAYQEQ (ORCPT ); Wed, 25 Jan 2017 11:04:16 -0500 Received: from mail2-relais-roc.national.inria.fr ([192.134.164.83]:37248 "EHLO mail2-relais-roc.national.inria.fr" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750781AbdAYQEP (ORCPT ); Wed, 25 Jan 2017 11:04:15 -0500 X-IronPort-AV: E=Sophos;i="5.33,284,1477954800"; d="scan'208";a="257379462" Date: Wed, 25 Jan 2017 17:04:07 +0100 (CET) From: Julia Lawall X-X-Sender: jll@hadrien To: Joe Perches cc: Dan Williams , Bhumika Goyal , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] nvdimm: constify device_type structures In-Reply-To: <1485360117.12563.85.camel@perches.com> Message-ID: References: <1485285847-7006-1-git-send-email-bhumirks@gmail.com> <1485311842.12563.50.camel@perches.com> <1485312569.12563.52.camel@perches.com> <1485360117.12563.85.camel@perches.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > 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