All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] ftrace/scripts: Update the instructions for ftrace-bisect.sh
Date: Mon, 23 Jan 2023 17:45:41 +0000	[thread overview]
Message-ID: <Y87HxUN/mcC99Xj6@FVFF77S0Q05N> (raw)
In-Reply-To: <20230123121147.341b0992@gandalf.local.home>

On Mon, Jan 23, 2023 at 12:11:47PM -0500, Steven Rostedt wrote:
> On Mon, 23 Jan 2023 16:59:55 +0000
> Mark Rutland <mark.rutland@arm.com> wrote:
> 
> > > +# The old (slow) way, for kernels before v5.1.
> > > +#
> > > +# [old-way] # cat available_filter_functions > ~/full-file
> > > +#
> > > +# [old-way] *** Note *** this will take several minutes. Setting multiple
> > > +# [old-way] functions is an O(n^2) operation, and we are dealing with thousands
> > > +# [old-way] of functions. So go have  coffee, talk with your coworkers, read
> > > +# [old-way] facebook. And eventually, this operation will end.  
> > 
> > Super-trivial nit, but the above step isn't actually that expensive, and it's
> > the subsequent write to set_ftrace_filter that's going to be slow.
> 
> How about:
> 
>  "*** Note *** this process will take several minutes to update the filters." 

Sounds good to me! :)

FWIW, with that:

Acked-by: Mark Rutland <mark.rutland@arm.com>

> > That double spacing in 'go have  coffee' looks odd; is that an old error from
> > reformatting a line break, and/or a missing 'a' ?
> 
> I can fix that.

Thanks!

> > How about:
> > 
> > # [old-way] *** Note *** writing function names to set_ftrace_filter will take
> > # [old-way] several minutes. Setting multiple functions is an O(n^2) operation,
> > # [old-way] and we will set thousands of functions. So for subsequent steps,
> > # [old-way] go have a coffee, talk with your coworkers, read facebook. And
> > # [old-way] eventually, this operation will end.
> > 
> > ... or leave this in place below, and add "If using [old-way] ..." to the start?
> 
> I wanted to explicitly show that the above is only a reference to the old
> way, and leave no doubt about it. It was either doing this or deleting it
> completely. I chose to keep it.

Fair enough!

Mark.

      reply	other threads:[~2023-01-23 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 16:22 [PATCH] ftrace/scripts: Update the instructions for ftrace-bisect.sh Steven Rostedt
2023-01-23 16:59 ` Mark Rutland
2023-01-23 17:11   ` Steven Rostedt
2023-01-23 17:45     ` Mark Rutland [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y87HxUN/mcC99Xj6@FVFF77S0Q05N \
    --to=mark.rutland@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.