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 37FF51FF16B for ; Tue, 15 Jul 2025 14:04:54 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2C4813A906; Tue, 15 Jul 2025 14:05:50 +0200 (CEST) Message-ID: <7228bfcc-2828-47da-a156-8b894bfaca53@proxmox.com> Date: Tue, 15 Jul 2025 14:05:41 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Proxmox VE development discussion , Thomas Lamprecht , Friedrich Weber , Stoiko Ivanov References: <20250710125029.149536-1-f.weber@proxmox.com> <175215442892.1703641.2644485389391494179.b4-ty@proxmox.com> Content-Language: en-US From: Fiona Ebner In-Reply-To: <175215442892.1703641.2644485389391494179.b4-ty@proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL -0.028 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_MSPIKE_H2 0.001 Average reputation (+2) 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" Am 10.07.25 um 15:33 schrieb Thomas Lamprecht: > 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.. IIRC, it's mailman who eats the line endings, not git [0]. If you send a mail with such line endings to yourself it works without '--transfer-encoding=base64' too, but it doesn't work if you send it to the list. [0]: https://lore.proxmox.com/pve-devel/c72e637b-2e92-2ff5-0bc5-0c99d55b2ec8@proxmox.com/ _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel