From: Thomas Lamprecht Date: Sun, 12 Nov 2023 15:33:18 +0000 (+0100) Subject: d/rules: disable CONFIG_WQ_CPU_INTENSIVE_REPORT for now X-Git-Url: https://git.proxmox.com/?a=commitdiff_plain;h=248716e28cb67a23e5dc8b3a73b4797c61822750;hp=c0a8921e190852a5475d948f52cc04fac25946d7;p=pve-kernel.git d/rules: disable CONFIG_WQ_CPU_INTENSIVE_REPORT for now it's mostly noise for users, and quiet some interpret this as real problem and report it to us. Ideally we'd either educate them, or take time ourself, to report this upstream and see if the situation can be improved overall, but currently that's not feasible. We should check this out a few releases down, if the lower hanging fruits got fixed and noise got lower we could enable it again to catch the more rare cases. Signed-off-by: Thomas Lamprecht --- diff --git a/debian/rules b/debian/rules index 78b7f77..c9a2a3c 100755 --- a/debian/rules +++ b/debian/rules @@ -99,6 +99,7 @@ PMX_CONFIG_OPTS= \ -e CONFIG_PAGE_TABLE_ISOLATION \ -e CONFIG_ARCH_HAS_CPU_FINALIZE_INIT \ -d CONFIG_GDS_FORCE_MITIGATION \ +-d CONFIG_WQ_CPU_INTENSIVE_REPORT \ debian/control: $(wildcard debian/*.in) sed -e 's/@@KVNAME@@/$(KVNAME)/g' < debian/proxmox-kernel.prerm.in > debian/$(PMX_KERNEL_PKG).prerm