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 <t.lamprecht@proxmox.com>
This commit is contained in:
		
							parent
							
								
									c0a8921e19
								
							
						
					
					
						commit
						248716e28c
					
				
							
								
								
									
										1
									
								
								debian/rules
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										1
									
								
								debian/rules
									
									
									
									
										vendored
									
									
								
							@ -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
 | 
			
		||||
 | 
			
		||||
		Loading…
	
		Reference in New Issue
	
	Block a user