[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jjR0bP0rGfUaYDEU8_vawo-HFKZOjOdTqkd2-w_OoPzw@mail.gmail.com>
Date: Thu, 8 Dec 2022 14:11:00 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Li,Rongqing" <lirongqing@...du.com>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>,
"daniel.lezcano@...aro.org" <daniel.lezcano@...aro.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"tony.luck@...el.com" <tony.luck@...el.com>,
"jpoimboe@...nel.org" <jpoimboe@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>
Subject: Re: [PATCH 2/2][v2] cpuidle-haltpoll: Build as module by default
On Thu, Dec 8, 2022 at 1:45 PM Li,Rongqing <lirongqing@...du.com> wrote:
>
> > Also, there is an interface for switching cpuidle governors at run time already, so
> > why can 't it be used to address this case?
>
>
> I will study this interface, thanks
Sorry, this patch series is about the haltpoll driver, not the
haltpoll governor (which is there too), so you are right, it can be
modular, but it is not modular by default.
I guess it would be fine to make it modular by default, unless there
are expectations regarding it being present on system startup in the
field and that part is unclear. I think it would be better to defer
this change until it can be clarified.
Powered by blists - more mailing lists