[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191220101848.2b64b224@gandalf.local.home>
Date: Fri, 20 Dec 2019 10:18:48 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Kirill Tkhai <ktkhai@...tuozzo.com>
Cc: Rasmus Villemoes <linux@...musvillemoes.dk>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org, Kirill Tkhai <tkhai@...dex.ru>,
"mingo@...hat.com" <mingo@...hat.com>,
"juri.lelli@...hat.com" <juri.lelli@...hat.com>,
"vincent.guittot@...aro.org" <vincent.guittot@...aro.org>,
"dietmar.eggemann@....com" <dietmar.eggemann@....com>,
"bsegall@...gle.com" <bsegall@...gle.com>,
"mgorman@...e.de" <mgorman@...e.de>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][PATCH 1/4] sched: Force the address order of each sched
class descriptor
On Fri, 20 Dec 2019 13:44:05 +0300
Kirill Tkhai <ktkhai@...tuozzo.com> wrote:
> My opinion is to better make some less beautiful thing in a single synchronous place,
> than to distribute the redundancy over all the code (especially, when it is asynchronous).
I very much subscribe to this notion. The TRACE_EVENT() and NMI code
does the same. Keep all other use cases simple by making it complex in
one locality.
-- Steve
Powered by blists - more mailing lists