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 4C1731FF187 for ; Mon, 14 Jul 2025 09:04:33 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 0972BF219; Mon, 14 Jul 2025 09:05:28 +0200 (CEST) Message-ID: <290b5527-d136-4898-8f6c-3fb65306dd13@proxmox.com> Date: Mon, 14 Jul 2025 09:04:54 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Thomas Lamprecht , pve-devel@lists.proxmox.com References: <20250710125029.149536-1-f.weber@proxmox.com> <175215442892.1703641.2644485389391494179.b4-ty@proxmox.com> Content-Language: en-US From: Friedrich Weber In-Reply-To: <175215442892.1703641.2644485389391494179.b4-ty@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.012 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% 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: Re: [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 10/07/2025 15:33, Thomas Lamprecht wrote: > 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! Thanks for the merge! > 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.. Oops, sorry about that, will keep this in mind for next time with a CRLF patch. > 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). I did mention I only got it to build on bookworm, but forgot to mention I only tested on bookworm too. My workstation is still on bookworm and I didn't have any luck getting split-lock detection to work in a nested setup (even with CPU type 'host', the PVE VM doesn't see the 'split_lock_detect' CPU flag). Should have made this more clear though, sorry for the confusion. > > [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