From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752490AbeEPOAJ (ORCPT ); Wed, 16 May 2018 10:00:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:38126 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751595AbeEPOAH (ORCPT ); Wed, 16 May 2018 10:00:07 -0400 Date: Wed, 16 May 2018 10:00:04 -0400 From: Steven Rostedt To: Masami Hiramatsu Cc: linux-kernel@vger.kernel.org, Ingo Molnar , Andrew Morton , Thomas Gleixner , Tom Zanussi , Clark Williams , Karim Yaghmour , Brendan Gregg , Joel Fernandes , Namhyung Kim , Yann Ylavic , linux-rt-users@vger.kernel.org Subject: Re: [PATCH v2 11/14] ftrace/selftest: Have the reset_trigger code be a bit more careful Message-ID: <20180516100004.1e9c774c@gandalf.local.home> In-Reply-To: <20180516215350.4fb775e101bc6a122bfe3282@kernel.org> References: <20180514205845.017925650@goodmis.org> <20180514205958.915494639@goodmis.org> <20180516215350.4fb775e101bc6a122bfe3282@kernel.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 16 May 2018 21:53:50 +0900 Masami Hiramatsu wrote: > On Mon, 14 May 2018 16:58:56 -0400 > Steven Rostedt wrote: > > > From: "Steven Rostedt (VMware)" > > > > The trigger code is picky in how it can be disabled as there may be > > dependencies between different events and synthetic events. Change the order > > on how triggers are reset. > > > > 1) Reset triggers of all synthetic events first > > 2) Remove triggers with actions attached to them > > 3) Remove all other triggers > > > > If this order isn't followed, then some triggers will not be reset, and an > > error may happen because a trigger is busy. > > Ah, right! > > Acked-by: Masami Hiramatsu Thanks! > > I think this should go into stable tree too. I wonder if I should break this into two patches then. One for the actions before attached, and one for synthetic events? Hmm, maybe not. As it can handle not having synthetic events, it should be OK to let the update go to a time when they were not there. Thoughts? -- Steve > > Thank you! > > > > > Signed-off-by: Steven Rostedt (VMware) > > --- > > .../testing/selftests/ftrace/test.d/functions | 21 ++++++++++++++++--- > > 1 file changed, 18 insertions(+), 3 deletions(-) > > > > diff --git a/tools/testing/selftests/ftrace/test.d/functions b/tools/testing/selftests/ftrace/test.d/functions > > index 2a4f16fc9819..8393b1c06027 100644 > > --- a/tools/testing/selftests/ftrace/test.d/functions > > +++ b/tools/testing/selftests/ftrace/test.d/functions > > @@ -15,14 +15,29 @@ reset_tracer() { # reset the current tracer > > echo nop > current_tracer > > } > > > > -reset_trigger() { # reset all current setting triggers > > - grep -v ^# events/*/*/trigger | > > +reset_trigger_file() { > > + # remove action triggers first > > + grep -H ':on[^:]*(' $@ | > > + while read line; do > > + cmd=`echo $line | cut -f2- -d: | cut -f1 -d" "` > > + file=`echo $line | cut -f1 -d:` > > + echo "!$cmd" >> $file > > + done > > + grep -Hv ^# $@ | > > while read line; do > > cmd=`echo $line | cut -f2- -d: | cut -f1 -d" "` > > - echo "!$cmd" > `echo $line | cut -f1 -d:` > > + file=`echo $line | cut -f1 -d:` > > + echo "!$cmd" > $file > > done > > } > > > > +reset_trigger() { # reset all current setting triggers > > + if [ -d events/synthetic ]; then > > + reset_trigger_file events/synthetic/*/trigger > > + fi > > + reset_trigger_file events/*/*/trigger > > +} > > + > > reset_events_filter() { # reset all current setting filters > > grep -v ^none events/*/*/filter | > > while read line; do > > -- > > 2.17.0 > > > > > >