[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <977d3c0e-0fa6-440c-9ade-dac8ad93b898@intel.com>
Date: Tue, 5 Dec 2023 07:27:59 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Rafael J. Wysocki" <rafael@...nel.org>,
David Woodhouse <dwmw2@...radead.org>
Cc: pdurrant@...zon.co.uk, bp@...en8.de, dave.hansen@...ux.intel.com,
hdegoede@...hat.com, hpa@...or.com, jalliste@...zon.co.uk,
juew@...zon.com, len.brown@...el.com, linux-kernel@...r.kernel.org,
mingo@...hat.com, peterz@...radead.org, rafael.j.wysocki@...el.com,
tglx@...utronix.de, usama.arif@...edance.com, x86@...nel.org
Subject: Re: [PATCH] x86: intel_epb: Add earlyparam option to keep bias at
performance
On 12/5/23 07:19, Dave Hansen wrote:
> We could, for instance just support this pair:
>
> intel_epb=auto (default, will hack performance=>normal)
> intel_epb=preserve (leave it alone)
>
> for now.
Oh, and in code, this is literally as simple as:
-early_param("intel_epb_no_override", intel_epb_no_override_setup);
+early_param("intel_epb=preserve", intel_epb_no_override_setup);
You don't even need to go looking for "=auto" if you only have one other
option.
Powered by blists - more mailing lists