From nobody Thu Apr 2 18:47:40 2026 Received: from relay.smtp-ext.broadcom.com (lpdvsmtp10.broadcom.com [192.19.144.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 048D41552FD for ; Thu, 26 Mar 2026 23:02:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.19.144.205 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774566126; cv=none; b=htAU44rvheUIzZyufNzsT9xcfOK86e0T2SKUpEOsdugUvJJq3MYKKzJxDlwo/8nDEX4DtzphJoKjHn3SqmSSLxdoYnGVjxpIrQpoc1nMfvk3ZaAY8jxeVx/Zod3/fv2sfuzsTOWF/W2ekvQ6zmMl40NI/cNhsRTdfdCVOCfWz0o= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774566126; c=relaxed/simple; bh=dOKpzFlkKq/lgWlmBFChcvZk9LOxisMFUUfH1fqecqQ=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=UcbGBjpocC8Wz3ddqVOiscJdpHFIKldE+uDi8+LhMVoCem8jSTtEY2sgQZ6nQZpmTxgmPuPgDl0H2ICBtCSpucxuwbT5O13fy0QxtuLCM1NiOHXnLcn7XZeZ2YRjepGqq7XLP2uwis6KEC/SGFyd4ZjwRG5W25/7C01Lf4pbREc= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=HODWGte9; arc=none smtp.client-ip=192.19.144.205 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="HODWGte9" Received: from mail-lvn-it-01.broadcom.com (mail-lvn-it-01.lvn.broadcom.net [10.36.132.253]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id EA926C0005FA; Thu, 26 Mar 2026 16:01:57 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com EA926C0005FA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1774566118; bh=dOKpzFlkKq/lgWlmBFChcvZk9LOxisMFUUfH1fqecqQ=; h=From:To:Cc:Subject:Date:From; b=HODWGte9wFIG7tPtngJCVw47yRpcSlKh8a+45y209EPtgHnkjluMgjxU/lg6hLIaB SoWarFKSRXNvzcpZ9Y82cGeF+EKAdzM+BsI+t4b/fQuS7Gn/b7bD0cvs//Y5l5In1e NWH7Qf/FcsYza8BSZmnkj95azX+ywuvBGqfHgzXo= Received: from fainelli-desktop.igp.broadcom.net (fainelli-desktop.dhcp.broadcom.net [10.67.48.245]) (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 mail-lvn-it-01.broadcom.com (Postfix) with ESMTPSA id 99394B6B; Thu, 26 Mar 2026 16:01:57 -0700 (PDT) From: Florian Fainelli To: linux-kernel@vger.kernel.org Cc: Florian Fainelli , Jan Kiszka , Kieran Bingham , "Peter Zijlstra (Intel)" , =?UTF-8?q?Thomas=20Wei=C3=9Fschuh?= , Thomas Gleixner , Anna-Maria Behnsen , John Stultz Subject: [PATCH] scripts/gdb: Fix lx-timerlist after tk_core macroification Date: Thu, 26 Mar 2026 16:01:42 -0700 Message-ID: <20260326230146.2246073-1-florian.fainelli@broadcom.com> X-Mailer: git-send-email 2.43.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Commit 22c62b9a84b8 ("timekeeping: Introduce auxiliary timekeepers") changed tk_core from being a C structure declaration to using a macro identifier. This resulted in "lx-timerlist" to be broken and unable to locate the "tk_core" symbol, fix that. Fixes: 22c62b9a84b8 ("timekeeping: Introduce auxiliary timekeepers") Signed-off-by: Florian Fainelli --- scripts/gdb/linux/timerlist.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/gdb/linux/timerlist.py b/scripts/gdb/linux/timerlist.py index ccc24d30de80..9fb3436a217c 100644 --- a/scripts/gdb/linux/timerlist.py +++ b/scripts/gdb/linux/timerlist.py @@ -20,7 +20,7 @@ def ktime_get(): We can't read the hardware timer itself to add any nanoseconds that need to be added since we last stored the time in the timekeeper. But this is probably good enough for debug purposes.""" - tk_core =3D gdb.parse_and_eval("&tk_core") + tk_core =3D gdb.parse_and_eval("&timekeeper_data[TIMEKEEPER_CORE]") =20 return tk_core['timekeeper']['tkr_mono']['base'] =20 --=20 2.43.0