On Thu, Jan 08, 2026 at 08:32:37AM +0100, Jan Beulich wrote: > On 07.01.2026 20:19, Marek Marczykowski-Górecki wrote: > > On Tue, Jan 06, 2026 at 09:25:14AM +0100, Jan Beulich wrote: > >> On 06.01.2026 02:03, Jason Andryuk wrote: > >>> no-hwp failed to disable HWP. But if there is no ACPI CPU data, it > >>> wouldn't work either. > >> > >> There isn't any "no-hwp" option that we would recognize, is there? Iirc HWP > >> isn't enabled by default, so simply not saying "cpufreq=hwp" should disable > >> the driver? (I already found the original report confusing in this regard, > >> hence why I preferred to not reply so far. I wonder if there are local > >> patches in use.) > > > > Qubes has a patch enabling HWP by default on supported platforms. > > In which case can you please tell the reporter how to properly disable use of > the driver? Iirc the to-be-expected "cpufreq=xen" was already tried, with no > effect.
Looking at the code, it should be cpufreq=xen,no-hwp (so ",", not ":"). -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab
signature.asc
Description: PGP signature
