[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YWmBs5fLO3F151cY@hirez.programming.kicks-ass.net>
Date: Fri, 15 Oct 2021 15:27:15 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Song Liu <songliubraving@...com>, linux-kernel@...r.kernel.org,
kernel-team@...com, acme@...nel.org, mingo@...hat.com,
Andrii Nakryiko <andrii@...nel.org>,
KP Singh <kpsingh@...nel.org>
Subject: Re: [PATCH] perf/core: allow ftrace for functions in
kernel/event/core.c
On Wed, Oct 13, 2021 at 12:47:31PM -0400, Steven Rostedt wrote:
> On Tue, 12 Oct 2021 14:42:21 +0200
> Peter Zijlstra <peterz@...radead.org> wrote:
>
> > On Wed, Oct 06, 2021 at 02:07:32PM -0700, Song Liu wrote:
> > > It is useful to trace functions in kernel/event/core.c. Allow ftrace for
> > > them by removing $(CC_FLAGS_FTRACE) from Makefile.
> > >
> > > ---
> > > We had some discussions about this last year [1]. Seems that enabling
> > > ftrace in kernel/events won't really cause fatal recursion in the tests.
> > > Shall we give it another try?
> >
> > I suppose we can give it a go..
>
> Did you want me to pull this into my tree? My tests usually stress perf
> along with ftrace.
Hurmph, I just pushed it out, but sure, throw it in.
Powered by blists - more mailing lists