Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 6 May 2019 10:00:30 -0400
From:   Joel Fernandes <joel@joelfernandes.org>
To:     Viktor Rosendahl <viktor.rosendahl@gmail.com>
Cc:     Steven Rostedt <rostedt@goodmis.org>,
        Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] ftrace: Implement fs notification for
 preempt/irqsoff tracers
Message-ID: <20190506140030.GA234965@google.com>
References: <20190504164710.GA55790@google.com>
 <20190505223915.4569-1-viktor.rosendahl@gmail.com>
 <20190505190133.49b5ea46@oasis.local.home>
 <b415ea04-e078-a73c-3609-56fb195841c3@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b415ea04-e078-a73c-3609-56fb195841c3@gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, May 06, 2019 at 01:54:04AM +0200, Viktor Rosendahl wrote:
> On 5/6/19 1:01 AM, Steven Rostedt wrote:
[snip]
> > Hmm, what about adding a notifier to tracing_max_latency instead? And
> > do it not as a config option, but have it always enabled. It would send a
> > notification when it changes, and that only happens when there's a new
> > max latency. Would that work for you?

That sounds like a much better approach. thanks,

 - Joel