This bug is awaiting verification that the linux-xilinx-
zynqmp/5.15.0-1029.33 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-done-jammy-linux-xilinx-zynqmp'. If the problem still
exists, change the tag 'verification-needed-jammy-linux-xilinx-zynqmp'
to 'verification-failed-jammy-linux-xilinx-zynqmp'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-xilinx-zynqmp-v2 verification-needed-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2052817
Title:
cpufreq: intel_pstate: Enable HWP IO boost for all servers
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
This is a public version of https://bugs.launchpad.net/bugs/2009321
Backport cpufreq: intel_pstate: Enable HWP IO boost for all servers
[upstream 1f5e62f5fb217f2c1e003236be7d03cf606c26c4 (merged in 6.4)] to
jammy.
[Impact]
Currently there is a CPU model check for Skylake desktop and server
along with the ACPI PM profile for performance and enterprise servers
to enable IO boost. Patch removes the CPU model check, so that all
current server models enable HWP IO boost by default.
The HWP IO boost results in improvements for IO performance on both
Ice Lake and Sapphire Rapid servers.
Phoronix review: https://www.phoronix.com/news/Intel-ICL-SPR-IO-Perf-
Boost
Upstream review Link: https://lore.kernel.org/linux-
pm/20230303041411.3161780-1-srinivas.pandruvada@linux.intel.com/
[Fix]
Upstream patch:
cpufreq: intel_pstate: Enable HWP IO boost for all servers 1f5e62f5fb217f2c1e003236be7d03cf606c26c4
was merged to fix this. This will be back porting it to jammy.
[Test Plan]
I have tested this code, as has Intel.
[Where problems could occur]
The risk for regression is low. The change is fairly narrow, and has
been upstreamed for some time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2052817/+subscriptions
Комментариев нет:
Отправить комментарий