[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181204142918.12c087b4@vmware.local.home>
Date: Tue, 4 Dec 2018 14:29:18 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Anders Roxell <anders.roxell@...aro.org>
Cc: mingo@...hat.com, Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
Kees Cook <keescook@...omium.org>,
Arnd Bergmann <arnd@...db.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] tracing: add cond_resched to ftrace_replace_code()
On Tue, 4 Dec 2018 20:25:31 +0100
Anders Roxell <anders.roxell@...aro.org> wrote:
> On Tue, 4 Dec 2018 at 20:21, Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > On Tue, 4 Dec 2018 14:19:08 -0500
> > Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > > > @@ -2435,6 +2438,13 @@ void __weak ftrace_replace_code(int enable)
> > > > /* Stop processing */
> > > > return;
> > > > }
> > > > + /*
> > > > + * Some archs calls this function with interrupts or preemption
> > > > + * disabled. Howeve, other archs don't and this can cause a
> >
> > typo "However". But could you write it this way:
> >
> > "However, for other archs that can preempt, this can cause an
> > tremendous unneeded latency."
> >
>
> I'll fix this and move it up (where I added it in the first place but
> moved it) =)
>
I also noticed a grammar issue:
"Some archs call this function .."
-- Steve
Powered by blists - more mailing lists