From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id B29BB48A44 for ; Fri, 31 Oct 2025 15:38:07 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AA2C640150; Fri, 31 Oct 2025 15:38:07 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 6ECEE40150 for ; Fri, 31 Oct 2025 15:38:06 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1761921486; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=irNj3LFPTjvUY8vhzcz08l758X9DhSOaqPl4P6bJynw=; b=Pj68xWFkwPEkZM9131qFDY5JEgq6mWF0dqNKoz+7LesTkOTfaspOXOsKmVC4ESrTUGhkvU /YepRnueAjxJA8yKUqfZhYs9dGvoFI/A6K6zPo7DoLnCf5+df+BwmmpOunsLTeYfmnSb8O gxWyll6iw6mMsPVwKomOAyEx8PmH2UA= Received: from mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (ec2-35-165-154-97.us-west-2.compute.amazonaws.com [35.165.154.97]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-621-DusrzNLmMNCHNpcsHELHOA-1; Fri, 31 Oct 2025 10:38:00 -0400 X-MC-Unique: DusrzNLmMNCHNpcsHELHOA-1 X-Mimecast-MFC-AGG-ID: DusrzNLmMNCHNpcsHELHOA_1761921479 Received: from mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.111]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-06.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 107F4180A972; Fri, 31 Oct 2025 14:37:59 +0000 (UTC) Received: from rh.redhat.com (unknown [10.44.32.50]) by mx-prod-int-08.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 69265180044F; Fri, 31 Oct 2025 14:37:57 +0000 (UTC) From: Kevin Traynor To: Sivaprasad Tummala Cc: Anatoly Burakov , dpdk stable Subject: patch 'eal/x86: enable timeout in AMD power monitor' has been queued to stable release 24.11.4 Date: Fri, 31 Oct 2025 14:33:11 +0000 Message-ID: <20251031143421.324432-69-ktraynor@redhat.com> In-Reply-To: <20251031143421.324432-1-ktraynor@redhat.com> References: <20251031143421.324432-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.111 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: 0Pf-SKjIGJQCvpFBRD3UEqNeG7KKBE4DxE8fD0Tl7CA_1761921479 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit content-type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Hi, FYI, your patch has been queued to stable release 24.11.4 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 11/05/25. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable/commit/4e309113126d8cf44cf2e50362ae590a176e07ac Thanks. Kevin --- >From 4e309113126d8cf44cf2e50362ae590a176e07ac Mon Sep 17 00:00:00 2001 From: Sivaprasad Tummala Date: Mon, 13 Oct 2025 05:51:57 +0000 Subject: [PATCH] eal/x86: enable timeout in AMD power monitor [ upstream commit 1213a8895be3bf883f10b3ba60ee84099b5ff75a ] Previously, the AMD power monitor implementation did not enable the timeout, causing the lcore to remain in a wait state until an external monitoring event occurred or an interrupt was received. This patch enables the timeout-based exit condition, allowing the lcore to automatically wake up after the specified period. The maximum supported timeout value is 2^32 - 1. Fixes: c7ed1ce04704 ("eal/x86: add power intrinsics for AMD") Signed-off-by: Sivaprasad Tummala Acked-by: Anatoly Burakov --- lib/eal/x86/rte_power_intrinsics.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lib/eal/x86/rte_power_intrinsics.c b/lib/eal/x86/rte_power_intrinsics.c index f7d558153e..b46e8c2aba 100644 --- a/lib/eal/x86/rte_power_intrinsics.c +++ b/lib/eal/x86/rte_power_intrinsics.c @@ -88,12 +88,12 @@ static void amd_monitorx(volatile void *addr) static void amd_mwaitx(const uint64_t timeout) { - RTE_SET_USED(timeout); #if defined(RTE_TOOLCHAIN_MSVC) || defined(__MWAITX__) - _mm_mwaitx(0, 0, 0); + _mm_mwaitx(2, 0, (uint32_t)timeout); #else asm volatile(".byte 0x0f, 0x01, 0xfb;" : /* ignore rflags */ : "a"(0), /* enter C1 */ - "c"(0)); /* no time-out */ + "b"((uint32_t)timeout), + "c"(2)); /* enable time-out */ #endif } -- 2.51.0 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2025-10-31 13:53:54.355466019 +0000 +++ 0069-eal-x86-enable-timeout-in-AMD-power-monitor.patch 2025-10-31 13:53:52.173523796 +0000 @@ -1 +1 @@ -From 1213a8895be3bf883f10b3ba60ee84099b5ff75a Mon Sep 17 00:00:00 2001 +From 4e309113126d8cf44cf2e50362ae590a176e07ac Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit 1213a8895be3bf883f10b3ba60ee84099b5ff75a ] + @@ -15 +16,0 @@ -Cc: stable@dpdk.org @@ -24 +25 @@ -index 489ad3983f..8a5f222aea 100644 +index f7d558153e..b46e8c2aba 100644 @@ -27 +28 @@ -@@ -90,12 +90,12 @@ static void amd_monitorx(volatile void *addr) +@@ -88,12 +88,12 @@ static void amd_monitorx(volatile void *addr)