Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Tue, 5 Apr 2022 09:38:59 -0400
From:   Steven Rostedt <rostedt@goodmis.org>
To:     Peter Zijlstra <peterz@infradead.org>
Cc:     Kees Cook <keescook@chromium.org>,
        Josh Poimboeuf <jpoimboe@redhat.com>, kbuild-all@lists.01.org,
        linux-kernel@vger.kernel.org, kernel test robot <lkp@intel.com>
Subject: Re: vmlinux.o: warning: objtool: stackleak_erase()+0x35: call to
 ftrace_likely_update() leaves .noinstr.text section
Message-ID: <20220405093859.05660166@gandalf.local.home>
In-Reply-To: <20220405080335.GC30877@worktop.programming.kicks-ass.net>
References: <202204042008.sCQbEmVS-lkp@intel.com>
        <202204041125.500C28FD8@keescook>
        <20220404152502.0621caf9@gandalf.local.home>
        <20220405080335.GC30877@worktop.programming.kicks-ass.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Tue, 5 Apr 2022 10:03:35 +0200
Peter Zijlstra <peterz@infradead.org> wrote:

> > I think I'll just send a patch to nuke the tracer. I'm sure Peter Zijlstra
> > will be happy when I do that. But I still want the profiler, as I find that
> > useful.  
> 
> It'll explode the moment Lai's entry rework goes through. That'll make
> us run C code before we switch to the kernel address space, so your
> counters will not exist/be-mapped and *BOOM*.

We could black list those areas. Just add:

#define DISABLE_BRANCH_PROFILING at the top of any file and it will not
do the profiling.

-- Steve