From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 4D03B1FF170 for ; Thu, 10 Jul 2025 18:50:47 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 600F138DD2; Thu, 10 Jul 2025 18:51:31 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Friedrich Weber Date: Thu, 10 Jul 2025 15:33:53 +0200 Message-ID: <175215442892.1703641.2644485389391494179.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250710125029.149536-1-f.weber@proxmox.com> References: <20250710125029.149536-1-f.weber@proxmox.com> MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.829 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DATE_IN_PAST_03_06 1.592 Date: is 3 to 6 hours before Received: date DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH edk2-firmware v2] fix #6430: backport patch to fix split lock detection warnings X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu, 10 Jul 2025 14:50:29 +0200, Friedrich Weber wrote: > On host CPUs with the split_lock_detect flag (newer Intel CPUs), > booting an OVMF VM with more than one core may trigger the host > kernel's split lock detection, as reported in [1]. > > With default settings, a kernel >= 5.19 slows down the corresponding > thread for 10ms when it detects a split lock operation, as documented > in [2]. A warning is logged, e.g.: > > [...] Applied, thanks! But I had to re-export the patch to get the \r\n line endings back, the reason for that is that you did not explicitly passed `--transfer-encoding=base64` to git send-email as the "auto" default value is seemingly not smart enough to go for that encoding when it sees such line endings.. btw. you git note suggested to me that you tried this on PVE 9, but you at least did not try to build there, as I had to fix a bit of stuff (mostly python 3.13 related). [1/1] fix #6430: backport patch to fix split lock detection warnings commit: 47055b2c7b56fecd84c6441c4f4c419738cc1df8 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel