[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220305140321.GW11184@worktop.programming.kicks-ass.net>
Date: Sat, 5 Mar 2022 15:03:21 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Phil Auld <pauld@...hat.com>,
Alex Belits <abelits@...vell.com>,
Nicolas Saenz Julienne <nsaenz@...nel.org>,
Xiongfeng Wang <wangxiongfeng2@...wei.com>,
Neeraj Upadhyay <quic_neeraju@...cinc.com>,
Thomas Gleixner <tglx@...utronix.de>,
Yu Liao <liaoyu15@...wei.com>,
Boqun Feng <boqun.feng@...il.com>,
"Paul E . McKenney" <paulmck@...nel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Uladzislau Rezki <uladzislau.rezki@...y.com>,
Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH 04/19] context_tracking: Rename
context_tracking_cpu_set() to context_tracking_cpu_track_user()
On Wed, Mar 02, 2022 at 04:47:55PM +0100, Frederic Weisbecker wrote:
> context_tracking_cpu_set() is called in order to tell a CPU to track
> user/kernel transitions. Since context tracking is going to expand in
> to also track transitions from/to idle/IRQ/NMIs, the scope
> of this function name becomes too broad and needs to be made more
> specific.
The previous patches did: s/context_tracking_/ct_/ on these names, and
this one makes it longer still?
Powered by blists - more mailing lists