On Fri, Oct 9, 2020 at 5:29 AM Chen Yu wrote:
>
> There is a corner case that if the intel_pstate driver failed to be
> registered(might be due to invalid MSR access) and with the acpi_cpufreq
> loaded, the intel_pstate sysfs might still be created, which makes the
> user confusing(turbostat for
Hi Srinivas,
On Mon, Oct 12, 2020 at 06:22:40AM -0700, srinivas pandruvada wrote:
> On Fri, 2020-10-09 at 11:30 +0800, Chen Yu wrote:
> > There is a corner case that if the intel_pstate driver failed to be
> > registered(might be due to invalid MSR access)
> Do you have logs why it is not loaded?
On Fri, 2020-10-09 at 11:30 +0800, Chen Yu wrote:
> There is a corner case that if the intel_pstate driver failed to be
> registered(might be due to invalid MSR access)
Do you have logs why it is not loaded? On supported platforms MSRs
should be invalid.
It may be a case when we are trying to
There is a corner case that if the intel_pstate driver failed to be
registered(might be due to invalid MSR access) and with the acpi_cpufreq
loaded, the intel_pstate sysfs might still be created, which makes the
user confusing(turbostat for example):
grep .
4 matches
Mail list logo