[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c759021-99ce-7633-699d-49b3229df339@csgroup.eu>
Date: Fri, 17 Jun 2022 11:44:49 +0000
From: Christophe Leroy <christophe.leroy@...roup.eu>
To: Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>
CC: "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Josh Poimboeuf <jpoimboe@...hat.com>,
"naveen.n.rao@...ux.vnet.ibm.com" <naveen.n.rao@...ux.vnet.ibm.com>,
"mbenes@...e.cz" <mbenes@...e.cz>
Subject: Re: [RFC][PATCH] ftrace,objtool: PC32 based __mcount_loc
Le 17/06/2022 à 13:24, Peter Zijlstra a écrit :
>
> Hi,
>
> I recently noticed that __mcount_loc is 64bit wide, containing absolute
> addresses. Since __mcount_loc is a permanent section (not one we drop
> after boot), this bloats the kernel memory usage for no real purpose.
I guess you mean it is 64bit wide on 64 bits architectures ? Because it
seems to be defined as 'long' so will be 32bit on 32 bits architectures ?
Christophe
Powered by blists - more mailing lists