search

QubesOS / qubes-issues

The Qubes OS Project issue tracker
https://www.qubes-os.org/doc/issue-tracking/
533 stars 46 forks source link

cpufreq=dom0-kernel not working #8907

Closed alibrs8531 closed 7 months ago

alibrs8531 commented 7 months ago

Qubes OS release

4.1.2 4.2 4.0.3

Brief summary

intel-pstate is off with cpufreq=dom0-kernel boot option. cat /sys/devices/system/cpu/intel_pstate/status shows it is off and I can't turn it on. cpupower also finds no cpufreq driver to use. I have tried this with older Qubes releases too like 4.0.3 version.

Steps to reproduce

add cpufreq=dom0-kernel boot option and trying to change /sys/devices/system/cpu/intel_pstate/status from off to active or on but getting error

Expected behavior

Being able to turn on intel-pstate with cpufreq=dom0-kernel or using cpufreq drivers with cpupower

Actual behavior

With cpufreq=dom0-kernel after changing /sys/devices/system/cpu/intel_pstate/status to active or on i get this error writing: /sys/devices/system/cpu/intel_pstate/status no such device.

DemiMarie commented 7 months ago

cpufreq=dom0-kernel is deprecated in Xen and known to be broken IIUC.

marmarek commented 7 months ago

Yes, and besides that, it isn't configuration we use nor support in Qubes OS.

github-actions[bot] commented 7 months ago

This issue has been closed as an "upstream issue." This means that the issue pertains to software that does not belong to the Qubes OS Project and that we do not develop or control. We suggest that you file this issue in the appropriate project's issue tracker instead. For more information, see Why don't you fix upstream bugs that affect Qubes OS?

We respect the time and effort you have taken to file this issue, and we understand that this outcome may be unsatisfying. Please accept our sincere apologies and know that we greatly value your participation and membership in the Qubes community.

If anyone reading this believes that this issue was closed in error or that the resolution of "upstream issue" is not accurate, please leave a comment below saying so, and we will review this issue again. For more information, see How issues get closed.

alibrs8531 commented 7 months ago

Yes, and besides that, it isn't configuration we use nor support in Qubes OS.

What do you mean by it isn't a configuration we use?

marmarek commented 7 months ago

What do you mean by it isn't a configuration we use?

None of the qubes tools add cpufreq=dom0-kernel option, nor is it recommended in qubes documentation.

alibrs8531 commented 7 months ago

cpufreq=dom0-kernel is deprecated in Xen and known to be broken IIUC.

Why was it deprecated?

DemiMarie commented 7 months ago

cpufreq=dom0-kernel is deprecated in Xen and known to be broken IIUC.

Why was it deprecated?

Only Xen has knowledge of overall system load.

alibrs8531 commented 7 months ago

cpufreq=dom0-kernel is deprecated in Xen and known to be broken IIUC.

Why was it deprecated?

Only Xen has knowledge of overall system load.

Can't it pass that info to dom0 or are there limitations?

marmarek commented 7 months ago

It isn't static info, it's info about system state in a particular moment and it changes in time. Yes, theoretically it could various different things, but it would be rather inefficient (and so - it doesn't). Anyway, that's offtopic on qubes issue tracker, it's more of a question to Xen developers.