[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220623200120.02e8ef43@rorschach.local.home>
Date: Thu, 23 Jun 2022 20:01:20 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Mark Rutland <mark.rutland@....com>
Cc: Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
linux-kernel@...r.kernel.org, Josh Poimboeuf <jpoimboe@...hat.com>,
christophe.leroy@...roup.eu, naveen.n.rao@...ux.vnet.ibm.com,
mbenes@...e.cz, Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Ard Biesheuvel <ardb@...nel.org>
Subject: Re: [RFC][PATCH] ftrace,objtool: PC32 based __mcount_loc
On Thu, 23 Jun 2022 15:21:30 +0100
Mark Rutland <mark.rutland@....com> wrote:
> I don't think that helps? I'm on about the size of the kernel "Image" file, not
> the runtime memory footprint.
>
> ... unless you mean doing that at compiler time?
Oh, when Peter said: "This saves, on an x86_64-defconfig + FTRACE,
23975*4 ~= 94K of permanent storage." I was thinking of "storage in
memory". I wasn't thinking of disk space on the host machine.
But sure, this is fine with me. I'll have to take a deeper look at the
patch though.
-- Steve
Powered by blists - more mailing lists