[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220517101351.273b385f@gandalf.local.home>
Date: Tue, 17 May 2022 10:13:51 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Li kunyu <kunyu@...china.com>
Cc: mingo@...hat.com, linux@...linux.org.uk, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, hca@...ux.ibm.com,
gor@...ux.ibm.com, agordeev@...ux.ibm.com,
borntraeger@...ux.ibm.com, svens@...ux.ibm.com, tglx@...utronix.de,
bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
hpa@...or.com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
linux-s390@...r.kernel.org, liqiong@...china.com
Subject: Re: [PATCH] kernel: Ftrace seems to have functions to improve
performance through optimization through optimization
On Fri, 13 May 2022 10:13:14 +0800
Li kunyu <kunyu@...china.com> wrote:
> Subject: [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization through optimization
Did you forget to add a subject line. The above looks to be the beginning
of the paragraph below.
> Date: Fri, 13 May 2022 10:13:14 +0800
> Message-Id: <20220513021314.59480-1-kunyu@...china.com>
>
> such as ftrace_ARCH_code_*, return 0, so the FTRACE_* check is not required
And even combined, the above makes no sense.
This patch is not an optimization patch. If it were, the optimization
provided is so small, it's not worth adding it.
Just state that it's a clean up (I already told you this). Here, I'll do
the work for you (but I expect a proper patch):
Subject: [PATCH v2] ftrace: Remove return value of ftrace_arch_modify_*()
All instances of the function ftrace_arch_modify_prepare() and
ftrace_arch_modify_post_process() return zero. There's no point in
checking their return value. Just have them be void functions.
There, that's what I would like to see.
-- Steve
>
> Signed-off-by: Li kunyu <kunyu@...china.com>
Powered by blists - more mailing lists