[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210414172602.GW3762101@tassilo.jf.intel.com>
Date: Wed, 14 Apr 2021 10:26:02 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Waiman Long <llong@...hat.com>
Cc: Alex Kogan <alex.kogan@...cle.com>, linux@...linux.org.uk,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>, will.deacon@....com,
arnd@...db.de, linux-arch@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
tglx@...utronix.de, bp@...en8.de, hpa@...or.com, x86@...nel.org,
guohanjun@...wei.com, jglauber@...vell.com,
steven.sistare@...cle.com, daniel.m.jordan@...cle.com,
dave.dice@...cle.com
Subject: Re: [External] : Re: [PATCH v14 4/6] locking/qspinlock: Introduce
starvation avoidance into CNA
> The CNA code, if enabled, will be in vmlinux, not in a kernel module. As a
> result, I think a module parameter will be no different from a kernel
> command line parameter in this regard.
You can still change it in /sys at runtime, even if it's in the vmlinux.
-Andi
Powered by blists - more mailing lists